By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
455,573 Members | 1,777 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 455,573 IT Pros & Developers. It's quick & easy.

Setup problem

P: n/a
Hi

When I build the setup project, I get the following message;

C:\myproj.vdproj 'shdocvw.dll' should be excluded because its source file
'C:\WINNT\System32\shdocvw.dll' is under Windows System File Protection.

Should I exclude the file or just ignore the message?

Thanks

Regards
Nov 20 '05 #1
Share this Question
Share on Google+
5 Replies


P: n/a
Exclude the file. There's no point in trying to install it because it won't
overwrite the one that's already on the system.
--
Phil Wilson [MVP Windows Installer]
----
"John" <jo**@nospam.infovis.co.uk> wrote in message
news:%2****************@tk2msftngp13.phx.gbl...
Hi

When I build the setup project, I get the following message;

C:\myproj.vdproj 'shdocvw.dll' should be excluded because its source file
'C:\WINNT\System32\shdocvw.dll' is under Windows System File Protection.

Should I exclude the file or just ignore the message?

Thanks

Regards

Nov 20 '05 #2

P: n/a
"John" <jo**@nospam.infovis.co.uk> scripsit:
When I build the setup project, I get the following message;

C:\myproj.vdproj 'shdocvw.dll' should be excluded because its source file
'C:\WINNT\System32\shdocvw.dll' is under Windows System File Protection.

Should I exclude the file or just ignore the message?


Why do you need this DLL?

<http://support.microsoft.com/default.aspx?scid=http%3a%2f%2fsupport.microsoft.c om%2fservicedesks%2ffileversion%2fdllinfo.asp&fp=1 >

--
Herfried K. Wagner
MVP VB Classic, VB.NET
<http://www.mvps.org/dotnet>
Nov 20 '05 #3

P: n/a
This message is usually generated because a file in your package is part of
Windows and therefore you are not suppose to redistribute it with your own
package. You can exclude it and rely on the fact that Windows on the
target machine already has the necessary file to make your app work.

Nov 20 '05 #4

P: n/a
Hi Phil,
Exclude the file. There's no point in trying to install it because it won't
overwrite the one that's already on the system.


OK, I exclude the file, and it builds. Now I check my WebDeploy
project into my CVS, and run my NAnt script on the build machine
(which always cleans out everything, then checks out everything clean,
and then starts a build), and the file is included again. How do I
exclude it in such a way so that it STAYS excluded?

Thanks,
Ed
Nov 20 '05 #5

P: n/a
Hi Guys,
OK, I exclude the file, and it builds. Now I check my WebDeploy
project into my CVS, and run my NAnt script on the build machine
(which always cleans out everything, then checks out everything clean,
and then starts a build), and the file is included again. How do I
exclude it in such a way so that it STAYS excluded?


Whoops, my mistake. Perhaps I did "save all" in VS.NET before checking
in. My problem - not VS.NET2003's.

Sorry,
Ed
Nov 20 '05 #6

This discussion thread is closed

Replies have been disabled for this discussion.