I was having license errors with the latest Marmalade (6.4) and I reran s3eConfig to fix them. I set it to use Visual Studio 2010 and it re-setup marmalade and the license errors went away. However it is not respecting my Visual Studio selection and always opens Visual Studio 2012.
So, my question is where does marmalade hide these config values that you set when running s3eConfig? It looks like I will have to change it manually.
Marmalade saves these values in AppData. But instead of modifying these values, you can just right click on the mkb and open them in your desired IDE disregarding the default ones.
I guess the Visual Studio 2012 is the phone version(wp8). Marmalade has a bug regarding this, don't remember the MAINT number/bug issue tracking number.
Related
I have installed Visual Studio 2015 Community Edition via Unity's installer and some of the options windows look like this:
Nothing fixes it; uninstalling-installing, formatting or installing on different machines. Apparently no one complains about this issue because there seems to be nothing on search results, but I'm 100% sure that everyone is experiencing this issue. When you open Visual Studio on its own, problem goes away, it works like it should. However, making Unity open Visual Studio causes it. I assume that this is caused by Unity forcing Visual Studio to load a plugin (probably Visual Studio Tools for Unity) which is actually incompatible with almost everything in Visual Studio.
Is there a solution to this problem? It drives me crazy and I don't want to use MonoDevelop.
I have a project from VS Studio 2010 that I want to work with in VS 2015. When I start this Project with VS 2015 I receive an error saying something like "compatibility-Error (Version)".
How can I successfully convert a Visual Studio 2010 project to use with Visual Studio 2015?
Without you going into any more detail about the actual error. (error numbers / screenshot) it will be very hard for any of us to give a real answer. Therefore I am going to suggest you take a look at Troubleshooting Unsuccessful Project Upgrades.
Something else to check out might be the Porting, Migrating, and Upgrading Visual Studio Projects guide
One of the key things mentioned in the 2nd link I provided is:
The following list describes support in Visual Studio 2015 and Visual Studio 2013 for projects that were created in Visual Studio 2012 or Visual Studio 2010 SP
Therefore I'd recommend upgrading the 2010 version to SP1 first. (if this is still installed that is)
One further thing to note is that if you keep the old version of Visual studio installed you can import a project which is made with an older version and skip the update. Visual studio 2015 will then use parts of the older version itself to open the project.
For details you can read How to: Upgrade Visual C++ Projects to Visual Studio 2015 page and the equally useful Installing Visual Studio Versions Side-by-Side page.
It appears that there are issues when moving from VS 2010.Net to VS 2015.Net and may require that you build the project from scratch and copy the code over. VS 2015 requires a Namespace. There are a number of designer issues on control that require the style page be used since various attributes have been removed. Something still, however, do work but you need to review the HTML, specifically things like Font and alignment. While it's a pain it isn't a big deal since it requires mostly cut and paste.
If you are having issues converting web projects the projects may have originally been created as a "web site" rather than a "web Project" . Try opening the application as a web site and see what happens. At least that may help get you to the point you can actually get to the code to convert it in VS 2015. Hope this helps.
Try to Right-click the solution, then select "Re-target solution".
I have the problem that Visual Studio 2013 crashes when I lock the computer or start another instance of Visual Studio.
I use Visual Studio 2013 with latest patches applied. I always start Visual Studio as Admin.
This seems to only happen with a certain big solution. This problem did not occur to me with other solutions.
I tried to delete the solution and make a clean checkout from TFS, but Visual Studio still crashes.
I know this is not much information, but do you have any idea how to fix this or how to what else I could check?
Additional Information: This still happens even with Visual Studio 2015 on a fresh Windows 8.1 installation...
Here's the error:
Use the following steps to solve the issue:
Source: http://resharper-support.jetbrains.com/entries/24765142-Visual-Studio-with-ReSharper-is-freezing-and-or-crashing
I would copy the solution with quotation but as you can see, there is a lot of text to edit.
Start Visual Studio using the /log switch. Then check the created log file for warnings and errors:
%APPDATA%\Microsoft\VisualStudio\11.0\ActivityLog.xml
If you use a Web Browser to view the file, it will be nicely formatted, due to the accompanying xsl-sheet.
I'm unable to open Marmalade MKB Files in Visual Studio 2013 Pro, while my other class mates can with the exact same version of Visual Studio. I've tried multiple projects but unfortunately I'am unable to open any. I've already tried to reinstall Marmalade.
The error message I get is:
Unsupported This version of Visual Studio is unable to open the
following projects. The project types may not be installed or this
version of Visual Studio may not support them.
Sounds like you may have set the mkb to be opened by visual studio as default instead of Marmalade.
So instead of Marmalade taking the mkb and turning it into a visual studio project and then opening it Visual Studio is just trying to open the .mkb file it doesn't understand.
Try right clicking on the mkb and choosing Open in Hub (or similar) from the context menu. You should be able to then open in IDE from there and have it open your project in visual studio. If you still get the same error then it means the problem is probably something else. If it works you'll have to stop visual studio being the default that will hopefully let marmalade take over again
Good Luck
I just joined a new project and the compiled source code of my team member has the Runtime version comment "4.0.30319.1" placed on every *.g.cs. I installed the latest visual studio with service packs and tried to run our project but suddenly my SVN icons have turned red on most files because Visual Studio 2010 automatically changed the Runtime Version comments to "4.0.30319.269" on all the *.g.cs files even though I did not change those files.
Is there a way to stop Visual Studio 2010 from doing this? I would change and commit all the changed files but then my teammate will have several files in red.
I know some may suggest to ask all team mate to install the same service pack and runtime, but I would like to know if this feature can be turned off.