Is there any way to get VS2012 set up for Enterprise Portal developing?
I already installed the EP Dev Kit for VS2010 and am able to build and deploy EP UserControls, but how to achieve this in VS2012?
MSDN says you have to use VS2010
Have I overseen something? Anybody knows about a workaround or something?
The complete solution and all referenced projects are built in VS2012 so it would be nice if there wasn't any need to have VS2010 involved for a single UserControl for AX.
As you said yourself, MSDN says:
Microsoft Visual Studio 2010 is required to create or modify User
Controls for Enterprise Portal
The visual studio components for AX don't work with VS2012 so you are stuck with VS2010. I don't know of any way to make it work but even if it was a workaround I would not recommend it since Microsoft says otherwise. You will not get support and you wouldn't be sure if any problems you face are due to using VS2012.
From that same page, these are the ones that are supported:
Visual Studio 2010 Professional, Visual Studio 2010 Premium, and
Visual Studio 2010 Ultimate.
It's not convenient but not a problem since you can run VS2010 and VS2012 side by side.
I am facing a problem in an attempt to debug the code in Visual Studio 2012. I have series of the class files and the Asp.Net pages in a single solution file. The Asp.Net pages call functions in the class libraries and get the required details.
Everything worked well until I upgraded my license from Visual Studio 2010 to Visual Studio 2012. The problem is that reference to the assemblies are lost and the build is failing. Additionally the Dlls after the compilation of the individual class file project are deleted.
Please let me know if someone has faced similar problem and resolution.
Thanks,
Yagya
I opened my vs2010 solution with vs2012 but it didn't make any conversion as from 2008 to 2010 was happening. So my solution still remains the same as 10 label on it. when I make a new solution of course it has 11 label on it. I haven't got any problem running like that but I am curious. Is there any difference? if yes, how to convert into vs2012 solution?
I managed to 'convert' the solution file to change the line containing '# Visual Studio 2010' to '# Visual Studio 2012' in the .SLN file.
Manual editing of the solution file is not necessary, or recommended. Simply open the VS2010 solution in VS2012, left-click the solution (at the very top of the Solution Explorer), then use File | Save As to overwrite the original file. This will effectively convert the VS2010 solution file to a VS2012 solution file.
There are some exceptions, but mostly you'll be able to open the same project and solution files files in both VS2012 and VS2010 SP1.
VS2012 may convert projects when you first open them, but the changes are (except noted in the document linked) backward compatible with VS2010 (ie using conditionals where needed to only apply to either version when loaded) Most project types will be left entirely untouched though.
It is about Visual Studio 2012 Compatibility
If you created your assets in Visual Studio 2010 with Service Pack 1 (SP1), many of them will load and run in Visual Studio 2012 without any further action on your part.
Many assets will also open again in Visual Studio 2010 with SP1 without any issues, even after you open those assets in Visual Studio 2012
For C++ projects it makes a difference, as the 2012 compiler (VC11) will only be used on projects that are explicitly 2012, not on 2010 projects opened in VS 2012. Some C++11 improvements are available with the VC11 compiler but not with VC10 (see this SO Answer for a summary), including:
Range based for-loops
New standard library headers (atomic, mutex, thread,...)
Smaller standard library container sizes
(And more to follow when the Nov 2012 CTP is delivered to VS 2012)
In order to convert from VS 2010 project to VS2012 there is no need to manually edit the solution file or 'Save As' over the existing project. Instead:
If you decline the update when first prompted, you can update the project later by opening the Project menu and choosing Update VC++ projects... [at the top of the menu options]
From MSDN's "How to: Upgrade Visual C++ Projects to Visual Studio 2012"
(This page was linked from #Joachim's MSDN link, but I wanted to have the answer here on SO since a number of other answers suggested manual workarounds instead of this VS 2012 feature)
In my case, I had some Visual Source Safe stuff (my project was created with Visual Studio 2003/2005, yes, very old!)
Once I manually removed the VSS stuff, the conversion succeeded.
PS: I know it's about VS2010, but maybe this helps others.
You can convert a project from VS2010 to VS2012 by doing the following:
Add the 2010 project to your VS2012 solution by right-click on your solution in the Solution Explorer and Select Add --> Existing Project...
The project will appear in the solution and will have (Visual Studio 2010) appended to its name.
Right-click on the added project and select Properties.
In the Configuration Properties --> General pane, change the setting in Platform Toolset field to Visual Studio 2012 (v110)
Repeat for each configuration type, e.g. Release and Debug.
I came across this question while googling for a solution to a specific problem: MSBuild was failing to execute the Publish target against a VS2012 solution that had started life in VS2010 when called from the command line (specifically through TeamCity):
error MSB4019: The imported project "C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v10.0\Windows Azure Tools\2.3\Microsoft.WindowsAzure.targets" was not found. Confirm that the path in the <Import> declaration is correct, and that the file exists on disk.
MSBuild was looking for the Azure SDK 2.3 targets in the VS10 location (C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v10.0\Windows Azure Tools\2.3\Microsoft.WindowsAzure.targets). The cause is explained by Sayed Ibrahim Hashimi in a blog post and, as I understood it, boils down to some decisions they made while enabling cross-version compatibility for solution files. The solution was simple: add the VisualStudioVersion property to the MSBuild invocation, something like this:
msbuild.exe MyAwesomeWeb.sln /p:VisualStudioVersion=11.0
Practically speaking, this overrides the following in each csproj file:
<VisualStudioVersion Condition="'$(VisualStudioVersion)' == ''">10.0</VisualStudioVersion>
Presumably you could get the same result by editing all of these by hand to replace 10.0 with 11.0 but that might break backwards-compatibility -- I haven't tried it. I also haven't tried an update to VS2013 to see if the problem persists.
So to wrap this up by answering the question: yes, there are some differences before you "convert" (using any of the methods offered by other answerers) and some differences remain afterwards.
This is slightly different, but along the same lines so in case it helps anyone:
I was loading a project where it looked like it was loading and then kept showing all projects as unavailable. No errors were on the migration report. I tried reloading the solution and projects many times, using various methods including suggestions here.
Finally I found a "Resolve Errors" option when right clicking on the solution in the Solution Explorer. VS went through a load process again and it worked; no problems.
I don't know what it did differently that time, but apparently it made a difference.
it's to simple just edit the .sol file
change the version to 11
like this
Microsoft Visual Studio Solution File, Format Version 12.00
Visual Studio 2012
Disclaimer: I am a total beginner to Visual Basic but code a bit in python and Drupal
I need to compile this C++ app (http://sourceforge.net/scm/?type=git&group_id=227253). I succesfully cloned from git, but how do I compile it (get the .exe) in Visual Basic 2008 or 2010 Express?
I have tried this:
1. Open Visual Basic 2008 Express, File, New, Windows Form Application (naive assumption, which should I choose?)
2. Dragged the contents of the git clone into the Solution Explorer Window (which Adds files)
3. Click Build menu
After that I'm lost. Any help is appreciated! This project uses cmake if that helps.
You need Visual C++, not Visual Basic. They are separate languages.
You cannot compile a C++ program in Visual Basic 2008 Express.
You must download Visual C++. Or purchase Visual Studio 2010 Pro (which includes all of VB, C++, C# and the web tools).
If you've got the bandwidth, I'd encourage you to get this .iso:
http://www.microsoft.com/visualstudio/en-us/products/2010-editions/express-iso
If you're interested in the "bleeding edge", MSVS 2011 beta is available here:
http://www.microsoft.com/visualstudio/11/en-us/downloads
Otherwise, if you just want to compile some C+ code on a Microsoft Visual Studio compiler, get this:
http://www.microsoft.com/visualstudio/en-us/products/2010-editions/visual-cpp-express
is there any way at all to open projects in Visual Studio 11 Beta without breaking their compatibility with Visual Studio 2010?
Maybe someone already wrote a tool that converts project files back to 2010 version?
I desperately wanna work in VS11, but all others in our team work in 2010,
Is there any tool that can convert project files back to VS2010?
If your team is using VS2010 SP1 then you are probably OK already. Visual Studio supports round tripping of solutions and projects between versions now so that you can open a project in VS11, make changes, and then open it in VS2010 without breaking anything.
More information can be found here: http://blogs.msdn.com/b/visualstudio/archive/2012/03/28/round-tripping-with-visual-studio-11.aspx and the compatibility list is here.
Maybe this work: http://vsprojectconverter.codeplex.com ?