Build Errors During deploy but not complie (kind of)

[Paul [Paradise Solutions]]

Hi all

I see this keep cropping up a lot, but not found any responses that
relate to my issue:
If I do a deploy of my project I get the
"There were build errors. Continue?"
message, and is accompanied with the following from the Output window:

------ Build started: Project: ConfigFileReader, Configuration: Debug
Pocket PC ------

Preparing resources...
Updating references...
Performing main compilation...
Building satellite assemblies...
Visual Studio is ready to deploy ConfigFileReader



------ Build started: Project: DBCreate, Configuration: Debug Pocket PC
------

Preparing resources...
Updating references...
Performing main compilation...
Building satellite assemblies...
Visual Studio is ready to deploy DBCreate



------ Build started: Project: PDASalesForms, Configuration: Debug
Pocket PC ------

Preparing resources...
Updating references...
Performing main compilation...
Building satellite assemblies...
Visual Studio is ready to deploy PDASalesForms



---------------------- Done ----------------------

Build: 2 succeeded, 1 failed, 0 skipped
Deploy: 0 succeeded, 0 failed, 0 skipped


If I click OK to proceed, the output ends up like this:

------ Build started: Project: ConfigFileReader, Configuration: Debug
Pocket PC ------

Preparing resources...
Updating references...
Performing main compilation...
Building satellite assemblies...
Visual Studio is ready to deploy ConfigFileReader



------ Build started: Project: DBCreate, Configuration: Debug Pocket PC
------

Preparing resources...
Updating references...
Performing main compilation...
Building satellite assemblies...
Visual Studio is ready to deploy DBCreate



------ Build started: Project: PDASalesForms, Configuration: Debug
Pocket PC ------

Preparing resources...
Updating references...
Performing main compilation...
Building satellite assemblies...
Visual Studio is ready to deploy PDASalesForms



------ Deploy started: Project: PDASalesForms, Configuration: Debug
Pocket PC ------




---------------------- Done ----------------------

Build: 2 succeeded, 1 failed, 0 skipped
Deploy: 1 succeeded, 0 failed, 0 skipped



If I just to a compile / recompile of the project I get ~no~ warning
message and the Output window is as follows:


------ Build started: Project: ConfigFileReader, Configuration: Debug
Pocket PC ------

Preparing resources...
Updating references...
Performing main compilation...
Building satellite assemblies...
Visual Studio is ready to deploy ConfigFileReader



------ Build started: Project: DBCreate, Configuration: Debug Pocket PC
------

Preparing resources...
Updating references...
Performing main compilation...
Building satellite assemblies...
Visual Studio is ready to deploy DBCreate



------ Build started: Project: PDASalesForms, Configuration: Debug
Pocket PC ------

Preparing resources...
Updating references...
Performing main compilation...
Building satellite assemblies...
Visual Studio is ready to deploy PDASalesForms



---------------------- Done ----------------------

Build: 2 succeeded, 1 failed, 0 skipped



Can anybody tell me how to find out what part is generating the error??

If I copy the compiled dll to the PDA and run my application I recieve
~no~ runtime errors.


Many thanks

Paul

 

[Ginny Caughey [MVP]]

Paul,

If you select Rebuild Solution, do you see any build errors?

--
Ginny Caughey
..Net Compact Framework MVP

 

[Paul [Paradise Solutions]]

No, task list is always clear and there is no mention of specific errors
in the output window

 

[Paul [Paradise Solutions]]

Sorry for not replying..

Turns out it was a dll version issue, although the compiler was not
telling me this in any windows. Wasn't untill I went through removing
projects from my solution and compiling them separately that I found the
issue.
Allthough *all* DLL references were 1.0.0.0 (they were being changed a
lot so I decided to just make them all the same to prevent version
issues) something some where was still storing a reference to
1.0.1245.12345 (for example), even after removing and re-entering
references. I had to delete the .vbproj.user file before the references
behaved themselves.


Paul

 

[Ginny Caughey [MVP]]

Thanks for the update, Paul. I'm glad you found the problem.

--
Ginny Caughey
..Net Compact Framework MVP