Re: VS2005 project files

Hi Will, 

> I use it quite a lot in TestMatrix, and made a variation of 
> the project parser code to handle this case by parsing both 
> build | platform sub-fields separately, but defaulting to 
> AnyCpu if nothing is available, which surprisingly someone 
> sent me a project file here recently that just had 'Debug' 
> but not Debug|AnyCpu.

I'm inclined toward that approach myself, but still not quite
sure how to deal with a platform that turns out to be non-executable
in the evironment where NUnit is running. 

Regarding bare Debug without a platform - does C# Express support
platforms? Maybe it creates projects that way. I'll test it when
I'm on a machine with express.

Charlie
 
> -----Original Message-----
> From: [email protected] 
> [mailto:[email protected]] On 
> Behalf Of [email protected]
> Sent: Monday, February 25, 2008 2:12 PM
> To: [email protected]
> Subject: nunit-developer Digest, Vol 21, Issue 37
> 
> Send nunit-developer mailing list submissions to
>         [email protected]
> 
> To subscribe or unsubscribe via the World Wide Web, visit
>         https://lists.sourceforge.net/lists/listinfo/nunit-developer
> or, via email, send a message with subject or body 'help' to
>         [email protected]
> 
> You can reach the person managing the list at
>         [email protected]
> 
> When replying, please edit your Subject line so it is more 
> specific than "Re: Contents of nunit-developer digest..."
> 
> 
> Today's Topics:
> 
>    1. NUnit and VS2005 Project Files (Charlie Poole)
>    2. Re: NUnit and VS2005 Project Files (Daniel M. Pomerantz)
>    3. Re: NUnit and VS2005 Project Files (Charlie Poole)
>    4. Syntax Layer Changes (Charlie Poole)
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Sun, 24 Feb 2008 17:54:49 -0800
> From: "Charlie Poole" <[email protected]>
> Subject: [nunit-developer] NUnit and VS2005 Project Files
> To: <[email protected]>
> Message-ID: <001c01c87751$6986d700$6401a8c0@ferrari>
> Content-Type: text/plain;       charset="us-ascii"
> 
> Hi All,
> 
> Some questions about a current problem...
> 
> A bug has been reported whereby configs for any platform 
> other than AnyCPU are ignored.
> 
> VS2005 allows creating multiple configs for multiple 
> platforms, so you could have a different property group for 
> Debug|AnyCpu, Debug|x86 and Debug|x64.
> 
> 1) Does anyone make use of this capability?
> 
> 2) How should NUnit create test configs when opening a file 
> with multiple platforms.
> If we create separate configs per platform, what names should 
> we use to distinguish them?
> 
> Charlie
> 
> 
> 
> 
> 
> ------------------------------
> 
> Message: 2
> Date: Mon, 25 Feb 2008 09:03:48 -0600
> From: "Daniel M. Pomerantz" <[email protected]>
> Subject: Re: [nunit-developer] NUnit and VS2005 Project Files
> To: Charlie Poole <[email protected]>
> Cc: [email protected]
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
> 
> ASSuming the following:
> 
> NUnit is a .Net application.
> 
> .Net is designed to be CPU independant.  It relies on the CLR 
> which can be written for any CPU.
> 
> Does it make sense to build a .Net application for any 
> platform besides "Any CPU?"
> 
> dmp
> 
> Charlie Poole wrote:
> > Hi All,
> >
> > Some questions about a current problem...
> >
> > A bug has been reported whereby configs for any platform other than 
> > AnyCPU are ignored.
> >
> > VS2005 allows creating multiple configs for multiple 
> platforms, so you 
> > could have a different property group for Debug|AnyCpu, 
> Debug|x86 and 
> > Debug|x64.
> >
> > 1) Does anyone make use of this capability?
> >
> > 2) How should NUnit create test configs when opening a file with 
> > multiple platforms.
> > If we create separate configs per platform, what names 
> should we use 
> > to distinguish them?
> >
> > Charlie
> >
> >
> >
> > 
> ----------------------------------------------------------------------
> > --- This SF.net email is sponsored by: Microsoft Defy all 
> challenges. 
> > Microsoft(R) Visual Studio 2008.
> > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> > _______________________________________________
> > nunit-developer mailing list
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/nunit-developer
> >
> >
> >
> 
> 
> 
> ------------------------------
> 
> Message: 3
> Date: Mon, 25 Feb 2008 09:42:59 -0800
> From: "Charlie Poole" <[email protected]>
> Subject: Re: [nunit-developer] NUnit and VS2005 Project Files
> To: <[email protected]>
> Message-ID: <008001c877d5$e17a30c0$6401a8c0@ferrari>
> Content-Type: text/plain;       charset="us-ascii"
> 
> Hi Daniel,
> 
> > ASSuming the following:
> >
> > NUnit is a .Net application.
> 
> Indeed. And designed to test other .NET applications.
> 
> > .Net is designed to be CPU independant.  It relies on the CLR which 
> > can be written for any CPU.
> 
> Yes.
> 
> > Does it make sense to build a .Net application for any platform 
> > besides "Any CPU?"
> 
> Apparently yes, given that people are doing it and Visual 
> Studio supports it. But, frankly, I don't quite understand it either.
> 
> I do know that for C#, the only difference between x86, x64, 
> IA-64 and AnyCPU is a flag in the header of the assembly. 
> That flag is used to determine which CLR will be used to run 
> the assembly and subsequently which GAC will be searched for 
> references. For C++ mixed assemblies, of course, the 
> difference would be more significant, but that's not what 
> this particular bug is about.
> 
> So what I'm looking for here is a better understanding of 
> what people are doing and why, since NUnit has to support 
> what its users are doing.
> 
> So, can anyone shed light on this?
> 
> Charlie
> 
> > dmp
> >
> > Charlie Poole wrote:
> > > Hi All,
> > >
> > > Some questions about a current problem...
> > >
> > > A bug has been reported whereby configs for any platform 
> other than 
> > > AnyCPU are ignored.
> > >
> > > VS2005 allows creating multiple configs for multiple
> > platforms, so you
> > > could have a different property group for Debug|AnyCpu,
> > Debug|x86 and
> > > Debug|x64.
> > >
> > > 1) Does anyone make use of this capability?
> > >
> > > 2) How should NUnit create test configs when opening a file with 
> > > multiple platforms.
> > > If we create separate configs per platform, what names
> > should we use
> > > to distinguish them?
> > >
> > > Charlie
> > >
> > >
> > >
> > >
> > 
> ----------------------------------------------------------------------
> > > --- This SF.net email is sponsored by: Microsoft Defy all
> > challenges.
> > > Microsoft(R) Visual Studio 2008.
> > > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> > > _______________________________________________
> > > nunit-developer mailing list
> > > [email protected]
> > > https://lists.sourceforge.net/lists/listinfo/nunit-developer
> > >
> > >
> > >
> >
> > --------------------------------------------------------------
> > -----------
> > This SF.net email is sponsored by: Microsoft Defy all challenges. 
> > Microsoft(R) Visual Studio 2008.
> > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> > _______________________________________________
> > nunit-developer mailing list
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/nunit-developer
> >
> 
> 
> 
> 
> 
> ------------------------------
> 
> Message: 4
> Date: Mon, 25 Feb 2008 09:42:59 -0800
> From: "Charlie Poole" <[email protected]>
> Subject: [nunit-developer] Syntax Layer Changes
> To: <[email protected]>
> Message-ID: <007d01c877d5$df6b4df0$6401a8c0@ferrari>
> Content-Type: text/plain;       charset="us-ascii"
> 
> Hi All,
> 
> One of the conclusions I reached from experimentation with 
> the 2.4 Assert.That syntax is that there are lots of 
> different opinions and that what works for one programming 
> language doesn't work for others quite as smoothly. For 
> example, the Is/Has family of helpers don't work well in C++.
> 
> So for 2.5 I'm trying to separate out the syntax into various 
> namespaces, allowing for various language families and for 
> the creation of alternative syntaxes by other folks.
> 
> What I've come up with so far is to replace the old 
> SyntaxHelpers namespace with a tree of namespaces rooted in 
> NUnit.Framework.Syntax. Right now, I have 
> NUnit.Framework.Syntax.CSharp, which contains all the 2.4 
> stuff, with the classes in NUnit.Framework.SyntaxHelpers 
> inheriting from the new ones for compatibility.
> 
> My basic idea is that /without/ any of the Syntax classes, 
> you could use the
> 
> classic asserts or Assert.That with "new 
> SomeTypeOfConstraint()" as an argument.
> If you want to create an extension-based syntax, a C++ 
> syntax, a BDD syntax, etc.
> then it would go into a sub-namespace of Syntax.
> 
> This is all just a first cut. What would you like to see?
> 
> Charlie
> 
> 
> 
> 
> 
> ------------------------------
> 
> --------------------------------------------------------------
> -----------
> This SF.net email is sponsored by: Microsoft Defy all 
> challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> 
> ------------------------------
> 
> _______________________________________________
> nunit-developer mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/nunit-developer
> 
> 
> End of nunit-developer Digest, Vol 21, Issue 37
> ***********************************************
> 
> 



-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/