I have a Windows 32-bit project designed in Visual Studio 2010 using C++. When I build and compile it on one computer, I get the GUI and the project works. However, on a different computer it only shows me a command prompt and then exits. What configuration changes do I need to make to see the GUI on this computer?
Related
In Visual Studio in Windows I can create a launchSettings.json profile which starts up an executable I specify and then attaches to it. Is it possible to do the same with an executable in WSL?
I'm writing an extension to a Linux program. The extension is a .Net 6 class library, so in order to debug it I need to start up the Linux program and then immediately attach. I could start up the program manually and then attach to the process from Visual Studio, but the extension loads first thing and I can't hop over to Visual Studio and attach fast enough to catch it.
I've found instructions for debugging .Net ASP and console apps in WSL from Visual Studio, but those instructions always assume that the project I'm debugging is itself executable.
Everything I've read about debugging C# programs on Windows Subsystem for Linux either uses Visual Studio Code, or tells you to launch the program through bash then attach the debugger to the process.
This method works, but it's slow to initiate every time I'd like to debug a change. Is there a way to setup Visual Studio to start remote debugging from the IDE similar to how it's done in C++?
You can debug the .Net Core application on WSL2 from Visual Studio 2019 now.
You need to install/update to version Visual Studio 2019 v16.9.1.
There are the Prerequisites, You can refer to Start debugging with WSL 2.
I have been building Smart Device application on Visual Studio 2008 and have been using a batch file to do so.
This has been working until I have installed Visual Studio 2015 and I wanted to still build and debug the solution via Visual Studio 2008 because Visual Studio 2015 doesn't support Smart Device development. However, using the same batch file I can no longer do so.
I am looking for a way to be able to target the devenv of the older version of Visual Studio for the batch file without uninstalling Visual Studio 2015, because I too have projects built on that version.
NOTE: I can run Visual Studio 2008 perfectly fine and using their on-click build tool it builds fine.
The batch file is probably picking up environment variables (INCLUDE, LIB etc) set up by VS 2015, which the 2008 toolset will not work with.
The Visual Studio 2008 menu should have a Visual Studio Tools submenu. Run Visual Studio 2008 Command Prompt from that submenu, which will open a cmd console with the VS 2008 environment set correctly. Run your batch file at that prompt.
You can automate it by writing a small batch file to first execute vcvarsall.bat (which is what the menu command does), then run your batch.
#call "<path-to-vs2008-install-directory>\vcvarsall.bat" x86
#call "<your-batch.bat>"
Hello I have created a DLL file using visual C++ 2010, that runs a C script that i have written.
I have then created a user interface using visual C# 2010 and linked everything together.
On my machine the resulting exe application runs perfectly.
However when i try to put the folder, containing BOTH the exe and the dll, on other computers.. it runs on some computers, but on others it does not.
the error i receive has to do with "Cant find dll file or assembly".
All computers have windows 7 64bit installed.
My question is: Is there a requirement for the application to run? (files or something that should be installed on all machines???)
I have noticed the following (after alot of looking) that:
the computers that run the application HAVE visual studio 2010 installed
the computers that do not run the application DO NOT have visual studio 2010 but have visual studio 2008 installed..
all computers have .NET framework 4.5 installed.
Do you think the visual studio has anything to do with this?!!? isnt the point having a stand alone application is to make the app run on any machine?
Is there a way to fix it so that the app will run on any computer regarding having visual installed or not?
thank you all..
You can use Dependency Walker to check what dll the program can't find.
Just load the .exe into the program.
You might also find that you will need to install the Visual Studio 2010 Redistributable on those computers that you are deploying to.
I have a project that suffers from a Visual Studio bug shown here
http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=356321
It means that I can't build the installer project on my windows 7 machine
(the workaround presented doesn't work for me, regcap.exe crahses when I try to run it)
Now I plan to build the installer on a remote XP machine or in XP mode. Can I do this without installing the full Visual Studio? What is the command line to build from a .vdproj file?
The obvious choice that comes to mind is using msbuild, but unfortunately it doesn't support building from .vdproj files. Another option without using Visual Studio is to use Team Foundation Build, if you have it installed or can afford to install it on one of your machines.
Ugly work around: move to wix - http://wix.sourceforge.net/