views:

84

answers:

3

about 10% of the time when I go to compile code that should compile, blend fails. I know the code should compile because w/o changing a thing it will compile in VS just fine. The really weird thing is that about 50% or more of the time, after compiling in VS and I come back to blend, it compiles. >_<

So, why does blend suck at compiling? and is there a way to make it as reliable as VS?

~N

A: 

Afraid I can't answer your question, other than to say that there ought to be no difference: both VS and Blend make use of MSBuild to compile.

I do have a gripe of my own, which is that Blend insists on building the whole solution, even though I typically have just one project that I'm changing in Blend - there's no option to build a single project (like there is in VS).

Samuel Jack
A: 

Like Sam said, my guess is that it doesn't have to do with the compiler but rather with the state of the project that's loaded. If you add a new class file in Visual Studio and then reference that class in an existing class, Blend will notice you've chanegd the existing class and prompt you to reload the file. But until you build in Visual Studio, it won't notice you've changed the project and added a new file.

Adam Kinney
+1  A: 

After some experimentation, I think I figured out how Blend makes its compilation decisions. Some of the oddities might be explained by my answer to this question.

Jacob