I'm trying to use an in-house custom tool that generates C# code from XML in Visual Studio.
The last time I successfully used the tool was about a month ago, since then I've updated from Windows 8.1 to Windows 10 and have also updated Visual Studio 2015 from Update 2 to Update 3. I have colleagues who were using Windows 10 and Update 3 before they installed the tool for the first time and there are no problems finding the tool for them.
There have been no changes to the tool made since updating Windows and Visual Studio.
When I tried to use it today I'm seeing the error
"Cannot find custom tool on this system".
I've tried uninstalling and reinstalling my tool, as well as calling devenv /setup, as well as deleting and readding the extension gallery for my custom tool. I've also tried repairing Visual Studio, to no avail.
I've checked the registry and I can see the key for the tool there.
Has anyone else experienced the same issue, or got any suggestions for other things I can try?
Thanks a lot!
The reason why the custom tool couldn't be found is because the strong name wasn't being verified.
I fixed the issue by running sn -Vr *,(missing public key) to add the assembly to the verification skipping list.
I don't know why the custom tool could be found prior to the Windows 10/Visual Studio upgrade. My best guess is that the verification list previously contained it and was lost whilst upgrading to Windows 10.
Related
I have a relatively large WinForms application that has been developed under Visual Studio 2013. I recently upgraded to Visual Studio 2015 on another computer and have been trying to get the project working under it.
My first issue/concern is that when I open the project for the first time in Visual Studio 2015 it does not ask me to "upgrade" the solution to Visual Studio 2015, it happily just opens the solution. I am used to having Visual Studio ask to "upgrade" the solution and create a new .sln file that is recognized as a, for example, Visual Studio 2013 solution instead of the old VS10 solution.
The actual issue I am facing is ~10 errors that seem to deal with cryptography. From what I can guess this has to do with the solution itself and what microsoft does with it in the background seeing as the most cryptography I use in the project is generating Guid.
An image of the errors
The one other issue I have is that, as I am not used to, I cannot double click on the errors them self to be lead to where Visual Studio thinks they are occurring. Thus I am not sure what is generating them or where to go from here.
Any suggestions?
This is a Windows 7 installation on an older model Lenovo Thinkpad. I do not have admin privileges on this computer either.
EDIT: So far I have tried to add <enforceFIPSPolicy enabled="false"/> to the file Visual Studio 15 settings at C\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\Devenv.exe.config, though whenever I try to edit it (even after a fresh restart) the file is "always" opened by another program. So it seems I cannot edit the file to turn off FIPS for Visual Studio 15.
I am still open to suggestions or clues.
EDIT2: I have managed to get <enforceFIPSPolicy enabled="false"/> into the IDE settings with the help of IT (Using this article). Though this seems to do absolutely nothing, it seems that it is being ignored.
Another issue/clue here is that even if I create a brand new C# project in Visual Studio, when I try to compile I receive the same errors. So I have to assume that Visual Studio is using the SHA256 class somewhere "in the background". If I did have control over its usage I would try to implement #Kevin 's answer below.
I have found another possible solution on the web though I am not sure of its validity
VS 2012 now builds C# projects in a separate process that runs
msbuild. The entry you added to devenv.exe.config (that worked for VS
2010) won't be seen by this process. You should add the same entry,
namely
to the config file for msbuild; typically that's found at
c:\Windows\Microsoft.Net\Framework\v4.0.30319\msbuild.exe.config"
I will try to get this done when I have time for the .NET 4.5+ msbuild.exe.config files and report back.
The solution I went with is outline here.
<enforceFIPSPolicy enabled="false"/> was added to a few files, namely
C:\Program Files (x86)\MSBuild\12.0\Bin\msbuild.exe.config
C:\Windows\Microsoft.Net\Framework\v4.0.30319\msbuild.exe.config
C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\Devenv.exe.config
Though I think the one that actually made it work was the first file.
You can't double click on the error and have it go to where the error is being thrown because it is being thrown inside the SHA256 class. If the FIPS compliance bit is set, any non-FIPS compliant .NET cryptography classes throw this error.
You have two choices to fix this...
First, you can just turn off the FIPS compliance bit on the machine where you are trying to run the app (not recommended).
Otherwise, you can update the code to use the FIPS compliant version of SHA256 (SHA256CryptoServiceProvider). This will require .NET Framework 3.5 or greater.
I just jumped back into a project that previously had no issues. We just upgraded to visual studio 2012. This morning I open my project to work on my code. I am getting designer issues all over the place.
"If this type is a part of your development project, make sure that the project has been successfully built using settings for your current platform or Any CPU"
It all seems to be coming from this platform issue. I have had zero issues in the past. I cannot find any information on how to fix this. I even go to open the designer on a file that previously worked (pre VS2012 install) and that fails.
So I went back to VS2010...without changing anything and attempted to open the same designer on the same file that previously worked and I also get an app crash.
Did somehow my visual studio 2012 install cause all of this?
Make sure that you are choosing the right CPU architecture for your designer. If it is ARM then you might see that message. You can check your CPU settings for your project like this:
I have a windows phone application build for windows phone 8, in Visual Studio 2012. I have started incorporating azure, and found that Visual Studio 2013, was a smarter choice for this. Therefore I installed the new VS, and opened the file, but I cannot get it to upgrade the solution.
I use the Visual Studio Version Selector as default opener, and it open the solution in my VS2013. But it is still VS2012 version, as can be seen on the picture:
I have tried to use Save as, which is stated as a solution here. But still the solution does not change. Anyone has a suggestion for how to upgrade the solution to VS2013?
What I want to use is what is shown in this video on Channel9. So I need to some how upgrade my project, or do I have to copy the code to a new project :-/ ?
I tried installing the SDK's from Microsoft Azure, but still no luck.
EDIT
The feature where you add connected service is not available for windows phone. And you do therefore not need to upgrade the VS solution. But still I had problems getting access to the server.
Go to "View", and click "Server Explorer". There one can see a windows/Azure logo, by clicking it you will add your windows azure account. apparently this does not mean adding your services even though it states that you are logged in and with the correct subscription.
Solution
However the solution I stumbled upon was to add a new Mobile Service. Where then get prompted to choose my subscription which then was not there. Apparently the subscriptions can be loaded in different ways. Therefore in this new popup under subscriptions choose import. And you basically get the route described.
After importing the subscription, you then cancel creating a new services(If you did not need it :)). And now all your azure stuff will be accessible to manage as seen in this link.
However it does not create the code lines since you are not using "add connected services" which is possible in windows apps.
Finally an answer :)
You cannot convert solution from Visual Studio 2012 to 2013 because it is not changed at all.
Sln is just xml file and it is remain same so there is no need to convert it from 2012 to 2013
I recently installed VS 2013 on Windows 8.1. When I open up any xaml file I get this error message below.
This happens even if I create a project from scratch in VS 2013. I've tried re-installing Windows 8.1 and VS 2013.
Has anyone come across this issue?
System.Exception Package failed updates, dependency or conflict
validation.
Windows cannot install package
App.a94e67374.a8775.a4662.ab57f.a7f1805386d2c because this package
depends on another package that could not be found. This package
requires minimum version 0.0.0.0 of framework
Microsoft.VCLibs.120.00.Debug published by any publisher to install.
Provide the framework along with this package.
I had the same error just like you.
I registered myself and got a developer licence. After registerering
I debugged the program and it all got fixed by itself
I use windows 10, to fixed it, I go to Setting -> Update & Security -> For developers, I choose Developer mode. In windows 8 and 8.1, I don't know.
the figure of setting
It happened to me as well with both VS 2013 and VS 2015. I think it's a common problem when VS is freshly installed.
I solved it both the times with running VS with administrator privileges (right click on the VS tile on Windows 8 and select "Run as Admin") and opening a XAML file with the editor. It takes some more time than usual, but then the problem gets fixed by itself.
After that you can continue using VS with standard user privileges.
Sadly none of the above solutions seemed to work for me.
My windows 8 installation is quite old and over the years, I had installed several visual studio versions such as 2010,2012 and 2013.
Even uninstalling visual studio, there will be many files and packages left behind.
I managed to fix this issue with the following steps:
1. Install Revo Uninstaller and from the options menu I enabled the "Show system components".
2. For some reason along with the visual studio 2013 ultimate installation (main application - do not uninstall this) I uninstalled two installations related to the main visual studio 2013 application such as: vs 2013 premium and vs 2013 professional apart from the main application (Repeat: Do not uninstall the main app)
3. Uninstall all the Microsoft Visual C++ runtime packages
4. Performed a repair of the the visual studio
Something else that I would rather prefer doing than performing a full repair as it takes far too long, would be to uninstall all the visual C++ runtimes packages and anything related to them (you might brake some apps but they are easy to find and easier to install)
and simply reinstall those visual c++ redistributes starting from the latest version and see if it works.
Before anything however, make sure you have a developer license like said on a previous post (no developer account is required. You don't have to pay for anything yet).
I'll try to provide step-by-step guid to fix the issue.
Please create an MSDN account here https://msdn.microsoft.com and use your login credentials in VS 2013
You have to enable "Developer mode" option from UPDATE & SECURITY (Windows 10). Attaching the screen shot for more clarity.
This should solve the problem, but if it doesn't then,
Try restarting your Visual Studio as administrator.
Some nice reads about configuring your device for development Windows 8 and Windows 10
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.