Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sample Solution #18

Open
drcrook1 opened this issue Dec 3, 2013 · 5 comments
Open

Sample Solution #18

drcrook1 opened this issue Dec 3, 2013 · 5 comments
Labels

Comments

@drcrook1
Copy link

drcrook1 commented Dec 3, 2013

Is there a sample solution that utilizes JSNLog that can be downloaded to see how everything works all put together. I am having issues putting everything together. I have several logging frameworks that I need to work with server side as well as a few custom ones.

Thanks,
~David

@mperdeck
Copy link
Owner

mperdeck commented Dec 4, 2013

Did you give the sample sites at
https://github.com/mperdeck/jsnlogSimpleWorkingDemos
a try?

Matt

@drcrook1
Copy link
Author

drcrook1 commented Dec 4, 2013

I did, there are 32 errors when attempting to simply compile the solution. It appears to primarily be reference issues. Things like Opimization does not exist in the namespace, WebActivatorEx could not be found, NLog could not be found etc. From the looks of it, it appears that the reference paths are looking for a relative packages folder at one level up from the solution, however that packages folder does not exist. I enabled nuget restore to no avail. Can you add the references into the correct locations into the downloadable package such that a fresh get will also pull the correct dependencies in the correct file structure? Or alternatively use Nuget to manage the restoration of those dependencies.

Post Edit:
It appears that you need to go into a project and manually restore the nuget packages via the manager ui and this will restore for all projects.

Next Issue:
Could not find schema information for the element 'log4net', 'appender', 'name', 'type' and lots more as well as 4 errors, 2 each in C:....\EmptyWebFormsWebsite - Log4Net and C:....\EmptyWebFormsWebsite\
the errors are: the type o rnamespace name 'WebActivatorEx' could not be found, all the errors are this same one.

@mperdeck
Copy link
Owner

mperdeck commented Dec 6, 2013

I reproduced and fixed the reference issues. Please give it another try:
https://github.com/mperdeck/jsnlogSimpleWorkingDemos

@justSteve
Copy link

Greets - I've just downloaded the repo (as zip) - extracted, cleaned solution and build fails, again on various references. But in JSNLog.Tests\JSNLog.Tests.csproj - Error 3 Could not copy the file "....\jsnlog.js\jsnlog.js" because it was not found.

Tried the zip referenced here and get:
Error 1 NuGet Package restore failed for project EmptyWebFormsWebsite - Log4Net(1): Unable to parse version value '' from 'packages.config'.. 0 0

Error 2 NuGet Package restore failed for project EmptyWebFormsWebsite(1): Unable to parse version value '' from 'packages.config'.. 0 0

@mperdeck
Copy link
Owner

mperdeck commented Apr 8, 2014

Hi Steve,

I guess you're referring to the JSNLog repo.

You're right, the zip download would have several broken links, as you found. Those links essentially point to resources local to my environment. I've been using Github as a way to backup my work, rather than to publish it to others.

I'm intending to clean this up. Meanwhile, here is how you can fix the broken links:

  1. Remove the "Empty..." projects from the solution
  2. Also remove the Website project - you don't need it to build JSNLog
  3. In JSNLog.Tests, from within Visual Studio, remove Scripts/lib/jsnlog.js. Although this looks like a file, it is actually a (broken) reference to a file, used in my local environment to update the jsnlog.js file from my jsnlog.js project. You'll find that the Scripts/libs directory actually contains the physical jsnlog.js file. After you've deleted the reference from within Visual Studio, the solution will build.

Matt

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants