Deployment Build problems

[Guest]

Out of no where I'm starting to get these problems and my Deployment projects
won't build anymore. Does anyone have any idea what's causing this? I've
tried copying these files from another VS.NET 2003 machine, but it doesn't
look like it's working. The only latest change I've made to my machine was
the Windows Update as of Feb. 8th, 2005. I notcied it included the .NET 1.1
SP1 and I don't know if this might have any relation?

ERROR Messages:

Unable to build dialog module named 'C:\Program Files\Microsoft Visual
Studio .NET 2003\Common7\Tools\Deployment\.\VsdDialogs\1033\VsdConfirmDlg.wid'
Unable to build dialog module named 'C:\Program Files\Microsoft Visual
Studio .NET
2003\Common7\Tools\Deployment\.\VsdDialogs\1033\VsdFinishedDlg.wid'
Unable to build dialog module named 'C:\Program Files\Microsoft Visual
Studio .NET
2003\Common7\Tools\Deployment\.\VsdDialogs\1033\VsdProgressDlg.wid'
Unable to build dialog module named 'C:\Program Files\Microsoft Visual
Studio .NET
2003\Common7\Tools\Deployment\.\VsdDialogs\1033\VsdWebFolderDlg.wid'
Unable to build dialog module named 'C:\Program Files\Microsoft Visual
Studio .NET 2003\Common7\Tools\Deployment\.\VsdDialogs\1033\VsdWelcomeDlg.wid'


Thanks,
Felix

 

[Guest]

Well, there was nothing at all in the KB and so I Googled the error message
(remember when you can search the KB with any error message and it was so
easy to find things?). Not much came up so I searched the Google Groups.

Turns out that one cause of the problem below is when the images on the
built in Deployment forms aren't pointing to the correct reference. The
image I had as the banner logo had an incorrect path and was causing it to
not compile.

With VS.NET out for a while and the post I read dated Apr 2004 you'd think
something like this would be in the KB by now, but I guess not.

-Felix

 

[Guest]

I had the same problem on on the 11th. The splash screen on my app came up,
but the main screen would not become visible (No error messages). The app
stayed in memory though and used 100% CPU.

This app was rock solid and unchanged. The behavior was experience on
current and older versions, compiled and debug versions, and on different PCs.

We think it may have be somehow related to do with latest Windows Update.