Visual Studio 2008 Multi-Targeting


Krzysztof Cwalina recently posted about a new set of FxCop rules that making it easier to use Visual Studio 2008 to target .NET Framework 2.0 and .NET Framework 3.0…  These rules let you know if any your code tries to call APIs that are only on your system and my not be on your client’s system yet. 

 

I’d love to year what you think! 

Comments (11)

  1. Krzysztof Cwalina recently posted about a new set of FxCop rules that making it easier to use Visual

  2. Tom Kirby-Green says:

    Hi Brad,

    Any chance of some FXCop rules that help us identify code with side effects, i.e. code that doesn’t lend itself well to a functional style of composition or code that might well be not such a great player when interacting with ParallelFX technologies like PLINQ?

    Kind regards,

    tom

  3. Josh says:

    The big pain point with multitargeting still exists:

    http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=299385

    Can you guys address this in a compelling way?

  4. Han says:

    Okay, dumb question… I know it’s always been pretty easy technically to have two versions of VS on one computer. I’ve had 2003 and 2005 before on 1 machine. And people seem to recommend keeping 2003 around for .NET 1.x stuff that needs to be maintained…

    But is it okay legally to do this? Say a company bought a copy of VS2003, and then only buys an "upgrade" of the license for VS 2008, meaning they still only have one license for that one developer.

  5. Mark Sowul says:

    I’m curious why the FxCop thing is necessary – isn’t that the point of VS’s multi-targeting?

  6. Chris says:

    Yet another reason why the decision to integrate FxCop only with the Visual Studio Team Edition for Software Developers seems so questionable

  7. BradA says:

    Mark – Yes, there is good multitargeting support in VS 2008 that catches 95% of the issues… These rules just help with the fringe cases.

    Han – While I am not an attorney, I think this is s fine configuration

    Josh – I hear you and I know the folks in VS have looked into this…

    Tom – That is a good idea, I will pass it on the FXCop guys

  8. As many folks know, .NET Framework 3.5 shipping a little later this year will include Service Pack 1

  9. As many folks know, .NET Framework 3.5 shipping a little later this year will include Service Pack 1

  10. Programming says:

    As many folks know, .NET Framework 3.5 shipping a little later this year will include Service Pack 1