I moved a lot of the java compile / packaging logic out of Build and into Packaging. This allows us to have a near instantaneous Build, and do all the slow linking/java/aapt stuff at Deploy time.
The downside of this is that many errors like this that should be build time errors don't show up until packaging/deploying is invoked. So now we're caught between 2 less than ideal options: - Have longer builds that actually show build errors correctly. - Have shorter builds that don't show some build errors until packaging/deploying. I am certainly open to opinions on which is preferable. Jonathan On 1/4/2012 10:59 AM, Wally McClure wrote: > I had some gotchas in a project that worked in 1.x and now doesn't work > as it did in 4.0.1. I had mixed in "-", "_", and numbers in the default > namespace and assembly name. The app would compile correctly, but > wouldn't deploy and the error messages that I got in the output window > looked like a compile error with these non alphanumeric. Is there anyway > to surface these type of deployment/compile time errors at the VS > compile time or is this something particular to Android that just > doesn't show up at the VS levels? > > Wally > > > _______________________________________________ > Monodroid mailing list > [email protected] > > UNSUBSCRIBE INFORMATION: > http://lists.ximian.com/mailman/listinfo/monodroid _______________________________________________ Monodroid mailing list [email protected] UNSUBSCRIBE INFORMATION: http://lists.ximian.com/mailman/listinfo/monodroid
