i have a C# project that i work on using visual studion 2013, the project was created with visual studio 2010, and the entire project is located on a local server and i am using Team Explorer to access it.
the problem is that if i make changes to the project and check-in the Solution (.sln) to the server, and my co workers, that use visual studio 2010, try to open the solution they get an error that the solution was created with a newer version of visual studio.
is there any way to force visual studio 2013 to not change the version number in the solution file? so even though i make changes to the solution the version will not change?
thanks for the help guys, i just ended up creating a copy of the solution file so i'll have 2 .sln files, one for each version.
not the best solution i hoped for but it'll have to do.
thanks.
Related
How do I open I a Visual Studio Code folder in Visual Studio 2015?
If I open it as a "Web Site", it tries to treat the node_modules directory as part of the project's normal JavaScript files and hits an error when the path exceed the maximum path length.
But I can't open it as any other project type unless I first create a project of that type and then move all the VS Code files into that folder.
Should I be trying to open it as a web site?
Or should I create a new project and then copy the files + folders into it?
Is there any advantage to having it as a project?
If I do create a project, it makes it difficult to work together with someone who is just using VS Code?
And if I use a project, which project type should I select?
Finally folder view has arrived in VS 2017 :)
You can find more details in here.
Currently there is no way to open a folder directly with Visual Studio.
Why? Because Visual Studio and Visual Studio Code only shared their name, not the idea behind it. To extend Jenny O'Reilly answer:
Visual Studio Code is a folder oriented editor
This means VSC has the same Point-of-View to your Project as the File Explorer.
Visual Studio (not Code) is a solution oriented integrated development environment (short IDE)
Instead every Project in Visual Studio needs a *.sln Solution-File as Root Component. From this point Visual Studio looks at your Project. An example would, if you copy File in your Project Folder, they wouldn't be recognized from Visual Studio. You have to add them first to your sln File, to see them. It also allows the developer to combine multiple projects (*.csproj,..) into one single Solution to build.
This means the idea behind these two editors is completely different.
Visual Studio (not code) Project-types for Web
There are Node.js Tools for Visual Studio
This will provide Node.js built-in project templates
Visual Studio 2015 comes with TypeScript templates
Workaround 1
A workaround would be a Blank Solution in which you set up your Visual Studio Code Project.
Workaround 2
Another trick would be the answer to this question. You can open your Project Folder as a Website Project.
File -> Open Website -> File System and choose the folder
Update
As you mentioned, there will be errors because Visual Studio tries to build the solutions. For the next few readers of this response, the work around for this (as John Pankowicz writes in the comment) is:
Right-click Web Site in Solution Explorer -> Property Pages -> Build -> Uncheck "Build Web Site as part of solution"
Update 2
(Thanks to JC1001 for this update)
The next version of Visual Studio (Visual Studio "15") will support opening a folder. This is mentioned in the Visual Studio Blog.
Also like in Visual Studio Code, there will be a prompt command for opening Folders. Right now you can use this in the preview version:
devenv /command “file.openfolder FOLDER_PATH”
In the future you will be able to use:
devenv FOLDER_PATH
Opinion
Personally I wouldn't recommend Visual Studio (not code) for HTML/Website projects without server-side-development, because I don't see any features. Even the intellisense suggests to me sometimes bad HTML Code (it's not the IDE's fault).
After all web projects are still text files. You can easily control group projects like this with Version Control. Visual Studio Code even provides an integrated Git support.
Visual Studio Code does not create "project files" that you can open in Visual Studio 2015. Basically, when you open up a Node website in Visual Studio, you need to re-create the folder structure in VS2015 and create a "project file".
I haven't seen any better ways of doing this, but will be happy when we can open a folder just as easilly as we can with VSCode
I'm sure it's not the best way but..
Open an existing .sln with notepad, change the names, save as [name of your project].sln.
Open with Visual Studio.
I am new to C# and have been trying to build digiCamControl on Visual Express 2013. The project CameraControl.Service is displayed as "incompatible" when building the solution. All other modules get added to the project without any problem.
1) Can you suggest why I could be facing this problem?
2) Can you suggest a fix for the problem?
Here is a link to the particular project inside digiCamControl, which is causing the "incompatiblity" error - https://github.com/dukus/digiCamControl/blob/master/CameraControl.Service/CameraControl.Service.csproj
3) Looking into this file, its a visual studio 2005 project (though opening it on some versions of Visual Express C# 2010, says that "you need a newer version" ?
< ProductVersion > 8.0.50727 < /ProductVersion >
(the id here is of visual studio 2005)
4) Do I need to migrate the project into 2013?
I want to use devenv.exe /upgrate to migrate the project - but it is not available on my Visual Studio C# 2013 (Community download) OR I cant find it.
I am downloading Ultimate Version to see if its available there.
Some other things, this is a WCF solution (if that helps).
Thanks in advance. ~ Naval
I was able to open the project and build it successfully with the Visual Studio Ultimate 2013.
Note: building successfully required some config changes, but those are more specific to the particular project (such as enabling unsafe operations).
I'm writing a customized activity for TFS build process workflow, e.g. guideline here.
The post requires to add reference to Microsoft.TeamFoundation.TestImpact.Client.dll at path C:\Windows\assembly\GAC_MSIL\Microsoft.TeamFoundation.TestImpact.Client\10.0.0.0__b03f5f7f11d50a3a. I cannot find this path on my machine installing Visual Studio 2012.
Where would I find this reference?
This is an old thread, but in case anyone else runs into this, just download the stand alone TFS Object Model installer.
As the other answer states, it's shipped with VS 2010 so you'll need to install that and then you should be able to find it.
For any of you trying to do this with VS 2013 / TFS 2013 you need Microsoft.TeamFoundation.TestImpact.Client version=12.0.0.0
This file is located in the folder
C:\Windows\Microsoft.NET\assembly\GAC_MSIL\Microsoft.TeamFoundation.TestImpact.Client\v4.0_12.0.0.0__b03f5f7f11d50a3a
Version 10.0 of the file is shipped with Team Explorer or Visual Studio 2010.
It is copied directly to the GAC but you can extract it using the command line COPY command.
Install VS 2010 on your machine, open a command prompt and navigate to C:\Windows\GAC_MSIL\Microsoft.TeamFoundation.TestImpact.Client\{Version}\
Then COPY Microsoft.TeamFoundation.TestImpact.Client.dll to a folder of your choice.
Finally, my advice would be that you use the version included in VS 2012, that would make things much easier. The method described above also works for Microsoft.TeamFoundation.TestImpact.Client.dll 11.0 (aka VS 2012 version).
A while ago I created a Visual Studio Package/Add-In for Visual Studio 2010 (for those curious: http://visualstudiogallery.msdn.microsoft.com/ea23f9a7-a942-45b2-87e6-5df6ff0444ff). If I try to download that and install it in Visual Studio 2012, it doesn't work, I get a version error.
So my first thought was to see what happens if I try to port it to 2012. I downloaded and installed the VS2012 RC SDK, and basically recreated the whole thing in a separate solution and it all works. What I noticed was that many of the assemblies I had to reference (Microsoft.VisualStudio.*) were now version 11 as opposed to version 10 (for obvious reasons). After copying and pasting all the code over, I got it to work correctly in Visual Studio 2012.
My question now is this: Is it possible to have one .vsix file for multiple versions of Visual Studio (I'm guessing no.) If not, what's the correct approach to take as far as uploading the different versions? Can I upload two versions of a .vsix? Will the Add-In manager in visual studio pick the correct one automatically? Do I need to create a new package e.g. "Visual Pastie 2012"? Just looking for some guidance.
Rename the VSIX package to give it a ZIP extension and open it up. You'll find a file called extension.vsixmanifest. Inside this XML file you'll find an element called SupportedProducts which should look like the following to work in VS2012.
<SupportedProducts>
<VisualStudio Version="11.0">
<Edition>Pro</Edition>
</VisualStudio>
</SupportedProducts>
HTH
I really really miss Object Test Bench in VS 2008 What's the equivalent of Visual Studio 2008 Object Test Bench in Visual Studio 2010?
so I'd like to be able to convert or maintain both solution versions in VS2010 and VS2008. Any tips to do so quickly or something maintainable (I mean without duplicating .cs files but only .sln) as I'm continuously adding classes in VS 2010 ?
At your OWN RISK (you do have a recent backup of your code or a source-control system, right??) - you can try this:
open up your solution file (*.sln) in Notepad or your favorite editor
change the first line from:
Microsoft Visual Studio Solution File, Format Version 11.00
to
Microsoft Visual Studio Solution File, Format Version 10.00
save that modified file as e.g. (yoursolution)_VS2008.sln
try and see if you can open the solution in VS 2008 again.
Between VS 2005 and 2008, only that one line in the SLN file changed - the project files (*.csproj, *.vbproj etc.) weren't touched. I haven't checked if that's still the case with VS2010 and VS2008.
I remember I converted VS 2008 solution to VS 2005 by just changing version in sln file (it is text file actually). try the same.
Unless your project is really, really big with complex settings, the surest most effective way is to just start a new 2008 project, and add your source-files to it.
It should only be 5 or 10 minutes of work, and you'd know for sure you had a proper 2008 project, instead of risking the problems that come with conversion.