If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpfull answers is nice, but saying thanks can be even nicer.
I have 3 installs of Visual Studio 2012 Pro. One on my main PC, one on my laptop and one on the ultrabook received as part of the competition.
The application being developed will run on the PC and the Laptop in Debug mode quite happily. On the ultrabook it throws Invalid Operation exception due to cross threaded calls. The project is identical on all 3 machines, as the code is pulled down from a central source control server.
When compiled (default Any CPU etc. options) and run the exe directly, the application runs fine on all 3.
There are no background workers etc. there is only the single thread.
I have not changed any settings on any of them, they are all the stock install and on first run of VS, the C# environment was selected as layout choice.
How the hell can I get to the bottom of this one? Any ideas?
Can we no longer step into private accessor methods in Visual Studio 2010 during unit testing? The debugger just skips over the method instead of stepping into the private method via MyClass_Accessor class.
I understand there are some issues with private methods in vs 2010's test framework, but is this problem I am having actually one of the issues?
I added a SQl 2008 Database project to my application. Then I created a new table script. When the script tab opens, VS hangs. I then get an error "Object reference not set to an instance of an object."
I created a 32-bit MFC application using VS2008 on a Windows 7 64-bit machine. Runs as expected. I copy just the EXE over to a Windows 7 32-bit machine, which has the VS2008 Redistributable Package installed, and get:
Ordinal Not Found
The ordinal 7138 could not be located in the dynamic link library mfc90u.dll.
Any idea on what's going on?
"One man's wage rise is another man's price increase." - Harold Wilson
"Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons
"Show me a community that obeys the Ten Commandments and I'll show you a less crowded prison system." - Anonymous
I'm not sure what exactly the incompatibility is between the two versions, but if you get a copy of Dependency Walker[^], you should be able to find out what function 7138 refers to, and why it is missing from the other system.
Unrequited desire is character building. OriginalGriff
I'm sitting here giving you a standing ovation - Len Goodman
I am working more toward development using the Visual Studio suite, specifically VB and C# .NET. I have always coded on 32-bit OS. What I want to know is that when you write something is VS I am sure its compiled in 32-bit, but would it run on 64? Do you have to buy a special version of VS to be able to have applications that are compatible with both types of processors?
There is no specific 64bit version of Visual Studio.
In your project properties, on the build tab there is an entry called "Platform target". In that dropdown, you can select the application target. The default is usually set to "Any CPU" which means that your application will build and be compatible to run on 32bit or 64bit systems. I'm not 100% sure, but fairly certain that you would have to have Studio installed on a 64bit system to have the x64 option in this dropdown which would specifically target 64bit systems.
That being said, 64bit systems will run the 32bit applications just find.
I wasn't, now I am, then I won't be anymore.
Last Visit: 31-Dec-99 19:00 Last Update: 15-Dec-17 14:46