Overview
Examples
Screenshots
Comparisons
Applications
Download
Documentation
Tutorials
Bazaar
Status & Roadmap
FAQ
Authors & License
Forums
Funding Ultimate++
Search on this site
Search in forums












SourceForge.net Logo
Home » U++ TheIDE » U++ TheIDE: Compiling, Linking, Debugging of your packages » Visual Studio 2012
Re: Visual Studio 2012 [message #39788 is a reply to message #38333] Sun, 28 April 2013 11:59 Go to previous messageGo to next message
keltor is currently offline  keltor
Messages: 73
Registered: February 2012
Member
Lance wrote on Sat, 23 February 2013 21:01

This is the 3rd time I have to refer to this post to set up for VS2012.

Upgrading upp will erase the build method. This time I'll make sure that I copy the bm file to a safe place.


That has happened to me a few times as well. I'm finding myself using U++ more and more, across all computers I have access to, so I need to re-create the VS11 options over and over. For everyone's convenience, here's a zip file with the MSC11 and MSC11x64 .bm files with the default options (as they appear in the first post).

Just unzip them in your upp folder (where your theide.exe resides).



281264 wrote on Mon, 10 December 2012 23:38

After some tests, the MSC 2012 do not seem to work fully well with TheIDE; for instance, it does not debugg correctly.




I have tried the debugger again with VS 2012 and it seems to work. I can set breakpoints, examine the variables, evaluate expressions and step the program execution, which is all I personally ask from my debugger. All this from within theide. I am running VS 2012 Express SP1 and U++ rev 6001.
  • Attachment: MSC11.zip
    (Size: 0.88KB, Downloaded 403 times)

[Updated on: Sun, 28 April 2013 12:03]

Report message to a moderator

Re: Visual Studio 2012 [message #39793 is a reply to message #39788] Mon, 29 April 2013 04:01 Go to previous messageGo to next message
nlneilson is currently offline  nlneilson
Messages: 644
Registered: January 2010
Location: U.S. California. Mojave &...
Contributor
keltor, your initial setup was very helpful.

When updating Upp I just rename the upp directory to the build number like upp6000. Install the update. Open both up and copy the build data from the previous to the new.

The less thinking required the 'more better" I like it.

I copied from you initial thread and put it in a file upp_changes.txt along with what is necessary to keep the FindReplace from vanishing and useful tips from this forum.
Re: Visual Studio 2012 [message #40690 is a reply to message #39788] Mon, 02 September 2013 22:32 Go to previous messageGo to next message
281264 is currently offline  281264
Messages: 269
Registered: June 2010
Location: Spain
Experienced Member
Quote:

I have tried the debugger again with VS 2012 and it seems to work. I can set breakpoints, examine the variables, evaluate expressions and step the program execution, which is all I personally ask from my debugger. All this from within theide. I am running VS 2012 Express SP1 and U++ rev 6001.


I have tested the compiler in 32 bits and it works fine and it debugs fine as well; but when it comes to work with 64 bits, it fails and produces the following error message:

Error creating process
C:\upp\out\MyApps\MSC11x64.Debug.Debug_Full\prueba_vectors.e xe
Windows error: Solicitud no compatible (NON COMPATIBLE SOLUTION)

Have you got the same problem?

Javier
Re: Visual Studio 2012 [message #40699 is a reply to message #37499] Thu, 05 September 2013 08:28 Go to previous messageGo to next message
keltor is currently offline  keltor
Messages: 73
Registered: February 2012
Member
Same problem here Javier
Re: Visual Studio 2012 [message #40913 is a reply to message #37499] Mon, 07 October 2013 12:22 Go to previous message
keltor is currently offline  keltor
Messages: 73
Registered: February 2012
Member
This topic is a bit obsolete now that there is "native" support for VS 2012 directly in U++; however, I have confirmed that the debugger still does not work in 64 bit version. Most likely, although I haven't looked at the code, it is trying to run the x64 debugger from a x86 executable, which AFAIK is not allowed.

File as bug?
Previous Topic: [Solved] Default compiler flags
Next Topic: Feature request: build flags to resource compiler
Goto Forum:
  


Current Time: Wed Nov 13 13:44:17 CET 2019

Total time taken to generate the page: 0.01865 seconds