"Carlo Capelli" <carlo.capelli@rdbos.net> wrote in message
news:XjGFf.70695$av6.51759@tornado.fastwebnet.it...
> Hi all.
>
> I upgraded the development of our application to Visual Studio 2005, and
> now
> I can't deploy
> it to some server configuration.
> The application comprises some .EXEs and .some .DLLs (MFC extension DLLs).
>
> Up to Visual Studio 2003, installing the application on the server
> required
> only to copy the EXEs & DLLs in the same folder, with the following
> minimal
> MFC-MSVC DLLs set (MFC71.dll, MSVCP71.dll, MSVCR71.dll).
> This worked well on both Windows2000 server and Windows2003 server.
>
> Using VS2005, this minimal set is (mfc80.dll, msvcp80.dll, msvcr80.dll). I
> found this coping just 1 of my EXEs on a Windows2000 server (with my MFC
> extensions DLLs), then attempting to start my EXE, I got the usual 'can't
> find DLL etc etc'. Copying the three files listed above solved the
> problem.
>
> On the customer test server (Windows2003 server) instead, I get a message
> like 'Incorrect system configuration: run the setup program etc etc'.
>
> It is to be noted that both the Windows2000 server and the Windows2003
> server have the .NET framework 1.1 installed.
>
> I'd like to be able gain the same behaviour as VS2003 (simple copy),
> because
> of the complexity (or impossibility) to run installation packages on our
> customers' servers.
>
> Anyone could help?
>
>

> This might be because you don't have a manifest file naming mfc80.dll and
> probably msvcr80.dll too. On VS 2005 you need to use manifests, and it can
> be embedded in the code file as as RT_MANIFEST.
>
> http://msdn2.microsoft.com/ms235264.aspx
> --
> Phil Wilson [MVP Windows Installer]
> ----
> "Carlo Capelli" <carlo.capelli@rdbos.net> wrote in message
> news:XjGFf.70695$av6.51759@tornado.fastwebnet.it...
> > Hi all.
> >
> > I upgraded the development of our application to Visual Studio 2005, and
> > now
> > I can't deploy
> > it to some server configuration.
> > The application comprises some .EXEs and .some .DLLs (MFC extension
DLLs).
> >
> > Up to Visual Studio 2003, installing the application on the server
> > required
> > only to copy the EXEs & DLLs in the same folder, with the following
> > minimal
> > MFC-MSVC DLLs set (MFC71.dll, MSVCP71.dll, MSVCR71.dll).
> > This worked well on both Windows2000 server and Windows2003 server.
> >
> > Using VS2005, this minimal set is (mfc80.dll, msvcp80.dll, msvcr80.dll).
I
> > found this coping just 1 of my EXEs on a Windows2000 server (with my MFC
> > extensions DLLs), then attempting to start my EXE, I got the usual
'can't
> > find DLL etc etc'. Copying the three files listed above solved the
> > problem.
> >
> > On the customer test server (Windows2003 server) instead, I get a
message
> > like 'Incorrect system configuration: run the setup program etc etc'.
> >
> > It is to be noted that both the Windows2000 server and the Windows2003
> > server have the .NET framework 1.1 installed.
> >
> > I'd like to be able gain the same behaviour as VS2003 (simple copy),
> > because
> > of the complexity (or impossibility) to run installation packages on our
> > customers' servers.
> >
> > Anyone could help?
> >
> >
>
>