I have Visual Studio 2013 Express version:12.0.21005.1REL with Team Foundation Server 2012 express installed.
I need to alter a Build Process xaml file however when I download from source control and open the file this happens:
The machine I am using is a 64bit system running a 64 bit windows 7 - but I am very surprised this should happen. How exactly do I go about altering this build process when the design view is not operable and the xml is horridly difficult to read / alter. Are there any resources which can help me?
Or is there anyway I can fix this?
Visual Studio is opening the xaml in split view to enable the visual designer to work. This link explains how to set VS to open xaml files in full text mode.
EDIT
I'm sorry, I misunderstood what you wanted to do. Seems this is a bug that has been reported with a possible workaround mentioned here and a relevant SO question here.
Related
Having this issue with visual studio for Mac - Can't load my configured environment variables.
If i run the app from a Terminal it works, but it doesn't if i run it from Visual Studio for Mac.
I added my variables to:
.bashrc
.bash_profile
I am using Visual Studio v8.7.8
(Yes, i tried restarting visual studio, even restarting the computer).
Any help is useful.
Thanks.
--EDIT--
I created the same post in Microsoft's dev community. Hopefully they fix this on the future. Stick to running VS from a Terminal for now.
So, unfortunately Visual Studio for Mac does not support using environment variables defined via bash or zsh (yet?...).
There is a hacky workaround by launching VS from a Terminal
/Applications/Visual\ Studio.app/Contents/MacOS/VisualStudio &
Launching it this way will allow VS to access user configured variables.
To make it easier to remember, an alias can be created by:
alias vs='/Applications/Visual\ Studio.app/Contents/MacOS/VisualStudio &'
Just remember to add this line to .bash_profile and .bashrc
Here is a Medium article on how to edit these files.
Here is a Blog post describing the VS issue.
I am using visual studio community 2017
Access 2010 - 2016
I can import an access file I created
File sent from client contains(tables, queries, forms, macros, and modules)
Provider=Microsoft.ACE.OLEDB.12.0;Data Source=C:\Users\jeremiah\Documents\Batching.accdb
The client sent me another basic file, was able to open without a problem
So I been through all current StackOverFlow solutions for people reporting the unrecognized database error and none of them have been useful.
My only theory is that the database they are using is to complicated to be used as a data source for visual studio.Do you have any suggestions?
I may not tell you what the problem is but I solved this issue before by resaving the database file as Microsoft Access 2003. Goto Save Database As Access 2002-2003 (*.mdb) and then use the new file.
You need use ACE.OLEDB 32 bits in Visual studio connection. (click in Advanced... button in Add Conection screen)
The visual studio try use of Jet.OleDB not more supported.
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 am getting the following error when trying to compile and test any type of project in Visual Studio 2012 Professional.
Error 1 The specified task executable "Csc.exe" could not be run. The
specified executable is not a valid application for this OS platform.
After testing multiple suggestions online nothing has fixed the problem. Anyone know what is causing this? Is there a new version of Csc.exe I need to get a hold of? I know this is the compiler just not sure what I need to do to fix the problem.
I had this exact problem today on my Win7 Machine. As Hans suggests, 'Navigate to C:\Windows\Microsoft.NET\Framework\v4.0.30319 and type "csc".'
The file may still exist but if you can open it with notepad, it will probably show just plain text of some errors. This is the indication that your compiler has been destroyed. At my office we have come up with a theory that a Windows update may be causing this because only a few machines have been affected, but I haven't read much online about it until now.
We fixed this by copying someone else's csc.exe into the C:\Windows\Microsoft.NET\Framework\v4.0.30319 directory and recompiling. Be sure to set the options on the file to read-only so this won't happen again. Good Luck!
The problems associated with csc.exe in Visual Studio 2012 can mostly be solved by repairing Visual Studio.
You need to repair Visual Studio. Go to Control Panel -> Programs. Then select your version of Visual Studio you are using and press "Change"(or right click it and press "Change"). When the setup appears, click "Repair".
I am on Visual Studio 2017 but this is the first google result that pops up for "csc.exe not found"
When I got this error I had to restart Visual Studio, being sure to select 'Run As Administrator'. Everything worked after that
I've faced this problem while i am trying to move Asp.Net Mvc Project from one computer to another ; error message was : The specified task executable location "c:\users\mypcname\documents\visual studio 2015\Projects\TestMVC\packages\Microsoft.Net.Compilers.1.0.0\build\..\tools\csc.exe" is invalid.
I solved this by
Creating new Mvc Project ;
going to that folder \Microsoft.Net.Compilers.1.0.0\build..\tools
and Copied the csc.exe file to my Projets >> \Microsoft.Net.Compilers.1.0.0\build..\tools\
i think when i was copying the project from the original Computer i left that csc.exe file in the specified folder.
Hope this will help someone.
Check your solution properties (right-click on Solution and select 'Properties') and make sure that the 'platform' field (Configuration Properties) is set correctly.
I think this problem is caused due to improper PC clean up. I was running Quick Heal PCTuner 3.0 software on a 64-bit windows 7 machine but suddenly due to loss of power my machine was shut down then when i opened it again I was getting this problem in VS 2013. Even TortoiseSVN checkout was not working and throwing internal error and something like corrupted disk also was shown when trying to delete some files on the harddisk.
I ran the PC Tuner again doing the Disk, Registry and traces clean up and it got fixed. maybe this problem may occur due to other cases also but is mostly related to the system's files In my case this is the fix
Regards.
in my case helped (I had .net framework 4.5.1 and vs c# 2010 express):
download the newest .net framework and run repair
On Visual Studio 2013, the same problem solved by doing this for me:
Right click the solution and open Configuration Manager. For the project(you may see at least one there), I've changed the Platform from Any CPU to x86 for the project that may causing the problem.
I've tried to delete and move csc.exe file but it doesn't do anything.
Then simply I upgrade .net version and than downgrade (returned to its original state) and it works.
I solved my problem by copying the whole folder containing my visual studio solution
From C:\Users\me\Google Drive...
To: C:\Users\me\OneDrive...
Basically, I had a project that was written with Visual Studio 2010 Express in C#, I then tried out using Visual Studio 2012 Express with that file, and now VS2010 says:
"The selected file is a solution file, but was created by a newer version of this application and cannot be opened."
Now when I had looked up about this, Microsoft said that you can still use 2010 if you do not use anything that was VS2012 specific. Well, I had tried out the built in Testing that is in the VS2012, and that was the only thing that was VS2012 specific, but deleting that from my project (the Testing project), still left it saying that it was created by a newer version.
So, how do you make a VS2010 solution that VS2012 modified work with VS2010 again?
SP1 for VS 2010 is required to open VS 2012 modified solutions.
Try this out:
http://vsprojectconverter.codeplex.com/
Personally I've never used it but I have it marked as a tool to use if I run into issues. Hope it helps!
This probably isn't the kind of answer you are looking for, but it has worked for me in the past for compatibility issues and such, so it's worth mentioning. If your project isn't too complicated, you can create a new project then copy and paste everything across, starting with form controls, and then moving to the code. It's a sloppy solution that doesn't scale well, but sometimes nothing else seems to work.
The response here by Andrew.Wu is very comprehensive
http://social.msdn.microsoft.com/Forums/en-US/vssetup/thread/fc763995-beed-4287-97de-6e47d3e87865 and details steps to take to solve the problem
very old...but hope it can help someone...
Step 1: Go to your project location where the project's sln file is kept and then Right-click on it, choose "Properties". Uncheck "Read Only" as like given below:
Step 2: Again Go to the location where the project's sln file is kept and then Right-click on it to open it with notepad and change the "Microsoft Visual Studio Solution File, Format Version 12.00" to "Microsoft Visual Studio Solution File, Format Version 11.00" on the file.
you can change also the "Visual Studio 2012" to 2010