I can't add System.Data.Linq or System.Web to project, each time I do I get a warning symbol yellow !, on the reference
Any ideas why?
I had it working all okay this morning
Did you change the .Net version of the project.
System.Data.Linq does not work for .Net 2.0.
you just need to go to solution explorer and right click on the references > add references > search for system.data.linq. Hope it work
Sounds like the path to the DLL may no longer be valid. Try removing the reference and adding it in again...
I've had to create a new project and copy the classes and now it is working.
Right-click your project, select "Properties", then hit the "Application" tab.
De-select "Client-only Framework subset". Grit your teeth at the annoying lack of detail you were getting before. (It just says "can't add reference".)
Related
I'm trying Azure Functions for the first time and have been able to build and publish "Release" versions without any issue.
I want to step through the code and so need to create and publish a "Debug" version but when I try and build I get the following errors with the same code:
CS0579 Duplicate 'System.Reflection.AssemblyCompanyAttribute' attribute
CS0579 Duplicate 'System.Reflection.AssemblyConfigurationAttribute' attribute
CS0579 Duplicate 'System.Reflection.AssemblyFileVersionAttribute' attribute
CS0579 Duplicate 'System.Reflection.AssemblyInformationalVersionAttribute' attribute
CS0579 Duplicate 'System.Reflection.AssemblyProductAttribute' attribute
CS0579 Duplicate 'System.Reflection.AssemblyTitleAttribute' attribute
CS0579 Duplicate 'System.Reflection.AssemblyVersionAttribute' attribute
From researching this error the main suggestion has been to remove them from the AssemblyInfo.cs file but rebuilds just put them back in again and the "Release" version is happy with these settings being there.
What am I missing so I can create a "Debug" version of the code?
Thanks
According to your description about CS0579 Duplicate error ,I suppose some temporary *.cs files generated during compilation got accidentally added to the project. The files were from the obj\Debug directory, you could try to delete these files to solve problem. For more details, you could refer to this SO thread.
In my case, some temporary *.cs files generated during compilation got accidentally added to the project.
The files were from the obj\Debug directory, so they definitely shouldn't have been added to the solution. A *.cs wildcard went a little crazy and added them incorrectly.
If it doesn't work, there are also other solutions you could have a try. Such as right click project name>choose Edit FunctionName.csproj. Edit the csproj and turn the generation of the attributes causing the issues off. More solutions you could refer to this article.
Resolution
I found this issue on GitHub where there were a couple of options to resolve this issue which I am going to cover here plus a third option I tried not mention in the issue.
I have managed to now get the Debug to build by following one of Janley's link and adding 4 extra lines into the .csproj file:
<GenerateAssemblyConfigurationAttribute>false</GenerateAssemblyConfigurationAttribute>
<GenerateAssemblyCompanyAttribute>false</GenerateAssemblyCompanyAttribute>
<GenerateAssemblyProductAttribute>false</GenerateAssemblyProductAttribute>
<GenerateAssemblyFileVersionAttribute>false</GenerateAssemblyFileVersionAttribute>
<GenerateAssemblyInformationalVersionAttribute>false</GenerateAssemblyInformationalVersionAttribute>
<GenerateAssemblyTitleAttribute>false</GenerateAssemblyTitleAttribute>
<GenerateAssemblyVersionAttribute>false</GenerateAssemblyVersionAttribute>
I have created a framework which I want to use in my OS X app. Since updating to Xcode 7 on El Capitan, when I try to command-click on the import statement, Xcode goes to the following view.
How can I get Xcode to display the Swift representation properly?
I've had it happen before, and my solution was to recreate every project file which I don't want to do again.
From my experience there are two possible causes for this issue.
The first one is that your framework can't be located. To fix this you need to go to target's Build Settings and add a path to Framework Search Paths either an absolute:
/Users/{user}/path-to-framework-parent-directory
or relative to project directory:
$(PROJECT_DIR)/path-to-framework-parent-directory
Another possible cause is that the path to your framework contains a space in it. I found that it doesn't matter whether you try to escape it with backslash ../Project\ Name/frameworks or take the whole path in double-quotes "../Project Name/frameworks". The result would be that SourceKit could not load the module.
Note that $(PROJECT_DIR) could expand to a path with a space in it and it would too result in the same error. So it looks like a bug in Xcode/SourceKit (I tried the latest Xcode 7.2-beta3 and the bug is still there).
My repository was on the second hard drive /Voluems/Macintosh HD/Repos. I just renamed the hard drive to HD, so the path looks like /Volumes/HD/Repos and the problem was gone.
Max S. answer pointed me in the right direction, however I was using the 'recursive' option for my framework path.
To get things to work I had to explicitly add a path to directly the framework in question's immediate parent directoy (as oposed to just having a path to one of its higher up directories with the 'recursive' option set).
HTH
I had this problem too and the other solutions didn't work. I finally figured it out in my case:
The target name cannot have a space in it either
To rename it:
Go to your project settings
Expand the target list column on the left if not already there
Click on the relevant target once (or press Enter or Tab when having it selected) and type in the new name without the space
Weirdly, just changing the name of my folder from 'Developer' to 'Development' fixed the issue from me.
Running Product->Clean, Product->Build is what worked for me.
In my case, I have created a framework for my SDK along with podspec for making it cocoa pod.
I had the same problem when i use my SDK and it fixed when I imported Foundation API to the file where I am consuming my SDK
import Foundation
Here is another potential solution - one that worked for me:
After importing the framework I never built for simulator, only for real devices. Swift Modules were not showing up, same error. Then I built for Simulator and it suddenly worked, I could see the Swift Modules.
The reason is that when I make my framework, I have a step that copies the swift modules from the iphonesimulator build to the universal build, but does nothing with the modules from the iphoneos build. So my guess is that this is why it didn't work.
Note: once I selected simulator and built it started working all the time, regardless of the build destination.
I need to download a json parser so I go to the jackson.codehaus.org website. Instead of a convenient link to click and download the jar/jars, they have me going in circles. Does anyone know where the jars are -- exactly?
You can use this link instead :
DOWNLOAD v2.9.7
More General Link
Or goto http://mvnrepository.com/ and search for 'jackson-core' .
If you click "Download" at the right edge of the screen, scroll down to "Downloads, 2.x" and click "Core", you'll get the direct download.
Here you can find the jackson libraries (version 2.4.0). I got these project from a tutorial where you can see how to implement jackson and the code and libraries are available to download too:
http://www.ibm.com/developerworks/java/library/j-hangman-app/index.html
Next alternative link : http://www.java2s.com/Code/Jar/j/Downloadjacksonall199jar.htm
You can find here the "AllIn" jars with complete list of included files. But latest version here is 1.9.9. so...
Please try
/repositories/snapshots/com/fasterxml/jackson/core
Goto relevant directory
jackson-annotations/
jackson-core/
jackson-databind/
Then open maven-metadata.xml file. You can find the directory of latest version there. Please note that all jars renamed with release date.
I know this question is 4 years old, but the Jackson library is still very hard to find, and even though Sujith PS' answer here leads to the core jar, that was not enough for me.
For anyone who's looking for the jar files for Core, Databind and Annotations, I found them here:
http://mvnrepository.com/artifact/com.fasterxml.jackson.core
Specifically for version 2.7.4:
jackson-core-2.7.4.jar
jackson-databind-2.7.4.jar
jackson-annotations-2.7.4.jar
I need to work with Json in mono and I'm using the IDE monodevelop.
How can I add as a reference json.net in monodevelop ?
In your project there should be a folder called References. Right click it and choose edit references. Then check the box next to the package you want to add
For monodevelop 4.012 try look in the Solution->Packages->Edit Packages
and look for the library you need.
When working on several AS3 projects that share a common code base, FlashBuilder seems to be losing workspace data when switching from one project to the next. I will often get a message that such class could not be found , when the class is actually in the path but was probably modified in the previous project.
To fix this error, I find myself having to remove the external library folder , restart FB, then re-add the library folder and all is well.
Please tell me there's another way to "refresh" FB's workspace ! Have you experienced anything similar? If yes, how do you avoid this problem?
Did you try a clean on the project?
project -> clean
You could also try to clean your workspace. In windows for example, just add -clean after the link to the exe.
Update:
on a mac, try this: http://www.brooksandrus.com/blog/2007/06/30/run-eclipse-from-the-command-line-on-os-x/