compile error when using vs professional

  • Thread starter Thread starter Tony Johansson
  • Start date Start date
T

Tony Johansson

Hello!

I think I have found something strange. We build a project with Visual
Studio Express 2010 successfully and then
the next day I install Visual Studio Professional 2010 and when I compile I
get compile error.

So I must ask if this is really possible. I mean if I can compile a project
in VS 2010 express successfully it must also
compile successfully in VS professional 2010 or what is the conditions ?

//Tony
 
I think I have found something strange. We build a project with Visual
Studio Express 2010 successfully and then
the next day I install Visual Studio Professional 2010 and when I
compile I get compile error.

So I must ask if this is really possible. I mean if I can compile a
project in VS 2010 express successfully it must also
compile successfully in VS professional 2010 or what is the conditions ?
Click to expand...

I expect both editions of VS to use the compiler that is part of the
framework itself (via msbuild).

So it does indeed sound strange.

What compiler errors are you getting?

Arne
 
Changes to the error logic in the compiler are rare, but they do happen.
Just read the "breaking changes" lists for compiler releases.
Click to expand...

But are Express and Professional using two different compilers?

Arne
 
No, I don't think so. My reply wasn't very well-worded. My point was simply
that differences can exist between versions, whether between releases (as
in the compiler and breaking changes) or between different SKUs of the same
release. It was an example, not specifically addressing the Pro/Express
issue.

That said, the Express edition does have limitations relative to the
Professional version (and any other retail version for that matter). I
would not expect to see actual compiler behavior differences (as it's using
the same compiler executable), but there could easily be differences in the
provided libraries or toolset that lead to different behaviors at
compile-time, even though the compiler is the same.

Assuming Tony is in fact not hallucinating, then there are pretty much two
possibilities:

-- The compiler is working exactly the same for both editions, but
receiving different inputs because of the Express/Pro difference, where the
inputs cannot compile in Express, but the _different_ inputs can compile in
Pro.

-- There's some other problem that has nothing to do with Express vs Pro,
where Tony has simply introduced a build break in his project when
transitioning between one version and the other.

As usual, without a concise-but-complete code example that reliably
reproduces the problem, along with specific descriptions of the exact error
message(s) being received, there's really nothing anyone else can do to
help. Clearly the behavior isn't impossible, because Tony has seen the
behavior.

Asking whether it's possible makes no sense whatsoever. What Tony ought to
be doing is posing a question that does make sense, along with sufficient
information for people to understand the question and offer advice and/or
answers.
Click to expand...

More info is certainly necessary.

Arne
 
Tony Johansson said:
Hello!

I think I have found something strange. We build a project with Visual
Studio Express 2010 successfully and then
the next day I install Visual Studio Professional 2010 and when I compile
I get compile error.

So I must ask if this is really possible. I mean if I can compile a
project in VS 2010 express successfully it must also
compile successfully in VS professional 2010 or what is the conditions ?

//Tony
Click to expand...

The only thing I have to add in addition to Peter's reply, is that I wonder
whether there might be differences between the project files for the two.
Rather than speculate can you tell us what compiler errors you got? Can you
also confirm that both Professional and Express were both up to date - VS
Professional should be at SP1, and whereas I don't use the Express version I
assume it should also be at SP1.
 
Back
Top