visual-studio-2003

I'm opening a solution that was apparently built on Visual Studio 2003 (not sure, I don't know anything about it) and trying to migrate to 2010. When trying to migrate I get the message: the application for project '' is not installed make sure the application for the project type (.csproj) is installed. If I open each one of the single projects of the solution they migrate fine but not the solution itself. If your projects individually migrate fine, then create a new blank visual studio 2010 solution, and add new projects individually (right click on solution->add->existing project) But I'm

I get the following message when I try to run a .net 1.1 web application in Visual Studio 2003: Error while trying to run project.Unable to start debugging on the web server. There is no managed code running in the process. In order to attach a process with the .Net debugger, managed code must be running in the process before attaching. Can any body tell what I am missing here. FYI : The application is working fine on the live server. Alex Filipovici Have you tried the following? Right click the ASP.Net project > Properties select Configuration Properties > Debugging Enable the below mentioned

Very blunt and to the point, but does anyone know how to convert a visual studio 2008 project to visual studio 2003, I'm meant to be delivering some stuff to a client and they only work in 2003. Sorry someone makes a very good point, what language, C# is the answer. I've done a bunch of searches on Google and tend to only come up with 2003->2008 and not visa versa, I would very much appreciate any help. It cannot be done in the general case, as the VS2008 project may use .NET 3.5 features that don't exist in .NET 1.1 used in VS2003. If you only have .NET 1.1 features in your VS2008 project,

In Visual Studio 2003, I am trying to set an environment variable in the pre-build event that will then be used in the compilation step, but the value doesn't seem to be propagated. For example, if the pre-build event contains this (either directly or within a batch file): set MY_LIB_VERSION=1.0.0 and AdditionalIncludeDirectories has this: c:\path\to\library\my_lib_v$(MY_LIB_VERSION)\include then I would expect the compilation to work if the my_lib_v1.0.0 directory exists. But instead, I get c:\path\to\prog\my_prog.c(22) : fatal error C1083: Cannot open include file: 'my_lib.h' Project :

So I have Visual Studio 2003 running on Windows 7 - yeah I am aware it isn't officially supported - and no, unfortunately I can't change that situation :-( For the most part it works OK but I have a specific problem, that I can't figure out. The application hangs if you do a project wide search (Ctrl - Shift - F) for a string. I have a reasonably powerful machine and all the other heavy tasks like compiling and debugging all work fine. It also works if I restrict the search to the current document (Ctrl - F). I am running it as administrator and VS.NET 2003 SP1 has been applied. The size of

I am working with a project which uses .Net Frame V1.1 runs on VisualStudio 2003, Now, I want to run my project in VisualStudio 2010? Can I still target .NET Framework 1.1 in VisualStudio 2010? Visual Studio 2010 only supports the 2.0, 3.0, 3.5, and 4.0 frameworks as targets. It does not support 1.1. Is there any reason why you can't upgrade it to .NET 2.0. Did you know that .NET 1.1 is no longer officially supported on Server 2008 R2 and so I wouldn't expect it to be officially supported on any newer operating system. I have read of some hacks to build .NET 1.1 projects for VS2005 and VS2008

I have an old dll that uses the Microsoft Visual C++ 2003 (7.1) run time package. Unfortunately I don't have that DLL around anymore. Short of reinstalling VS2003, is there another way to get the run time redistributable dll? BrainSlugs83 Storm's answer is not correct. No hard feelings Storm, and apologies to the OP as I'm a bit late to the party here (wish I could have helped sooner, but I didn't run into the problem until today, or this stack overflow answer until I was figuring out a solution.) The Visual C++ 2003 runtime was not available as a seperate download because it was included with

Yes, I know... I could set up a virtual machine running XP. Unfortunately our build environment is such that we need to be running VC2003, 2005 and 2008 concurrently and it would be much more convenient if I could run 2003 natively on Windows 7 for the few projects we have that require it. I realize some things may not be available in the IDE, but I was able to run 2003 under windows Vista and if I could get the same base level of functionality under Windows 7 I would be extremely happy. Right now I get an error opening the *.pdb file when I compile after switching vc2003 to run as