I created a solution using the previous VS now I have opened this Solution in VS 2010 and this reference seems to be incorrect:
It was fine before and the program has been running ok everyday for a couple of months; so why is the VS 2010 telling me this?
In the Solution Explorer it looks like something is wrong with the reference. Was fine before:
Ok - I've just deleted the reference above then found this build (which looks exactly the same) and added it and all seems good in the World now!
Have you referenced the office dll as well as just adding a using statement. Or if it has been running fine is the DLL missing or the reference been removed. Mostly likely cause is that the DLL was in the GAC of the machine it was developed on and it is not on the current one.
This is probably because the current version of VS hasn't the right dll loaded. So if I were you I would have look on how you can enable some of the references you need. I don't know how you can enable them, or which you have to enable. But I know I've had this problem before and it solved my problem.
Just Google the error and you will probably find the solution for it.
I recently installed the new VS therefore I believe it also installed the newest version of the .NET framework. So I suspect when I opened this project it was pointed at a more recent framework version which has caused a problem with the reference.
I deleted the broken reference and added it back in and it seems fine now.
Related
I just installed VS2015 community on my home machines. On my laptop, it works great. However I've run into an odd issue on my desktop. No matter what the reference is, it displays as unable to find (yellow warning symbol). It doesn't matter what or where it is. I have tried adding framework references (As basic as System) and references to external API DLLs in the local directory like Protobuf. NuGet will download packages referenced by projects I am working on and they will also be marked invalid. The properties for these references does not include a path, even when I specify one.
I'm a develop at work so I understand how to handle these issues generally. I've tried deleting the references and re-adding them, creating new solutions from scratch, pretty much everything I can think of and I'm out of ideas.
This is a Win7 machine with .NET 4.6.1 installed. I have tried changing my projects to target framework of 2,4,4.5,4.6, and 4.6.1 (no difference). This is a C# project if it matters.
Can anyone recommend next steps? Thank you.
I found the issue. Last month I tried to upgrade to Win10 and it didn't work out for me so I rolled it back. It deleted all the ACL information on all my directories. Specifically, the access to Microsoft.CSharp.Targets was lost. I restored that and everything worked again. Of course, now I have to try and fix every file and directory on my computer so I have access again. Thanks, Win10!
I'm having an issue with my solution finding project references after I pull the source code from TFS. After I get latest, I'll compile my solution and it will complain that it cannot find classes in other projects. These have been added as project references. When I check the references folder of the project that has the issue, the project reference is there and appears to be correct (properties look correct and I do no have the warning tooltip over the reference in the solution explorer) The only way I have been able to fix this is by removing the project reference then re-adding. As soon as I do that the errors go away even before I compile and all is well. I did some searching but was not able to find anyone with this specific issue. It seems to happen whenever someone adds in a new project into our solution then we get latest to get their changes. This will also happen on everyone's machine except the person who added the project. Once one of us goes through the steps of re-adding the references and commits those changes, it works for the rest of the team. All of use are adding project references like normal.
Here are the details of my development environment:
Windows 7
Visual Studio 2015 (v14.0.2317.0 D14REL)
C# .NET 4.6
TFS 2015
Resharper 10.0.1
I too faced similiar issue today. And now I understood the problem.... under 4.5 framework related project1 is referring superior framework 4.5.2 related project2.
So I did made them both as same and my solution started working..
Not sure whether same will work for you or not. Please verify on your solution as well.
I've installed the VS Community 2015 Update 1 but I'm not able to see the Web Project templates. I have done everything, reinstall, repair, reinstall the templates using devenv /installvstemplates, remove the ProjectTemplatesCache folder, pretty much everything I've found about similar issues but without results.
Any suggestion?
Thanks in advance
Well, the only thing that actually solved this issue: uninstall every single component manually installed (I assume that restoring the system to a previous point should work as well)...
I am writing a Visual Studio extension which targets VS2010, VS2012, and VS2013. It runs and is initialized successfully in each Experimental Instance with no issues. When I install the VSIX generated by the build, it installs in all versions without a problem, but only in VS2010 does it actually execute. In the others it's never instantiated or initialized.
There are no exceptions being thrown. Running the non-Experimental instance with the /log flag does not produce any other diagnostic information (other than confirming it is installed, and has a newer version than its counterpart already in the gallery.)
My reading and experiences suggest that this is due to some sort of missing assembly or reference, but I can't confirm that. I am also at a loss as how one would figure out what's missing, especially without an exception or log message.
I've been at this for several days now trying things like signing my assemblies, various vsixmanifest changes, changing the required framework versions, and many other things found here on SO that have not been fruitful.
Additionally, I have tried installing the old, already published version from the VS Gallery, and it also does not run. However, I have received feedback (bugs and thanks) from several individuals, so I know it works for some people. I have not received any feedback stating that "nothing happens," but do not rule out the fact that those are unreported.
I don't intend to plug, but the currently published version is here: http://visualstudiogallery.msdn.microsoft.com/5cc44f63-4ea8-4c17-8aa4-95037a2d32ef
The entire source for where I currently stand can be found on github in branch "ForStackOverflow". The difference between that and master is a TraceAppender which I used to confirm that the VSPackage was not being instantiated.
https://github.com/alexcpendleton/Pendletron.Vsix.LocateInTFS/tree/ForStackOverflow
Any suggestions, experiences, or anything would be helpful. Thank you.
Thanks to Erti-Chris Eelmaa's suggestion to enable FusionLog I was able to figure out what was going on.
Visual Studio was not looking for my extension in the installed extension's directory, rather from the GAC and elsewhere. Curiously, it was finding an included assembly just fine.
I examined the .vsixmanifest of other extensions and discovered that mine was missing a .pkgdef Content node for my project. It would seem VS2010 accounts for this, or for some other reason happened to look in the extension's installation directory for the package assembly, where 2012 and 2013 did not. Adding this content node to my .vsixmanifest allowed Visual Studio to load and run the extension.
<Content>
<VsPackage>Pendletron.Vsix.LocateInTFS.pkgdef</VsPackage>
</Content>
I'm getting started with WPF, but when I create a new WPF project (usuing all default options) it won't compile after VS generates the project. (Both under C# and VB) I believe I'm running the latest/greatest VS (which is maybe the problem?)
Microsoft Visual Studio Premium 2012
Version 11.0.60610.01 Update 3
Best I could tell none of the answers here provided any help at all. The namespaces/class names are all correct.
Did you change a file name at any point?
Try Rebuild (not Build).
Uninstalled the .Net frameworks and reinstalled them and everything works again! BTW, tried reinstalling VS and that had no effect, don't waste your time.
However, very shortly after this I ran into this problem:
Error Reading Resource File for any WPF Project in VS2012
However, it worked briefly before the problem started, so I'm not sure if this solution had anything to do with the new problem or not. Just be aware.