Re: Thinking Clearly

"David Clegg" wrote:
I.P. Nichols wrote:

Thanks for the links. Brian has also given me an excellent reference
into what .NET 3.0 consists of.

I agree and thank Brian, I wasn't aware of that excellent link.

As a database guy you may find this link of interest:
http://blogs.msdn.com/adonet/archive/2006/07/11/662447.aspx
ADO.NET vNext: The Entity Framework, LINQ and more

I thought we were expressly talking about .NET 3.0 here, and I'm pretty
sure I saw that LINQ is not going to be included (shipping with Orcas,
I believe).

Sorry, I didn't mean to suggest that ADO.NET vNext (aka ADO.NET 3.0) was
part of .NET 3.0 but wanted to point you to it because of it's recent
slightly turbulent history. And of course LINQ also isn't part of .NET 3.0
it just happened to be part of the overall subject of that link.

Since .NET 2.0 is going to be an integral part of .NET 3.0 it doesn't
need a new compiler but there are new compiler for WinFX.

Which is why I had my initial impression that .NET 3.0 may be easily
consumable by Highlander users. It seems that this may not be the case,
if large components require a design-time experience, and this
experience requires Visual Studio to work.

Actually it's msbuild that's the key that unlocks everything. You can
develop with any tools you wish and use msbuild provided the files are
proper. It works from the sln/proj files and you don't even need to have
Visual Studio installed - msbuild comes as part of the WinFX SDK. I often
use it to rebuild projects after a CTP WinFX update rather than loading the
project into Visual Studio. But if there have been breaking changes then I
need Visual Studio to help me find and correct them.

But don't forget there's a heckava lot more to WinFX than just WPF
which has been the focus of all the attention here on this newsgroup.

Well that was kind of the guts of my point. WPF would almost
undoubtably require some kind of design-time support. But I figure
there will still be plenty of other .NET 3.0 components which will be
of benefit to, and easily consumable by, Highlander developers.

You wanta speculate on what would some those other .NET 3.0 components might
be and how Highlander would support them? I ask because I have absolutely no
idea how this would work.



.

Relevant Pages

  • Re: Dotfuscator and ClickOnce
    ... Visual Studio uses MSBuild to build and publish ClickOnce ... Fortunately, there's a AfterCompile target, which is built after the ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Working With WPF in D2007/D2008?
    ... Maybe I'm being too persnickety but in the vernacular of both MSBuild and Visual Studio they are referred to as "Project" files. ... If you rename or delete the foo.csproj file and try to build with that same command line, MSBuild will complain with the error message "MSBUILD: error MSB1009: Project file does not exist." ...
    (borland.public.delphi.non-technical)
  • Re: Dotfuscator and ClickOnce
    ... This does not work with the Dotfuscator Community Edition shipped with Visual Studio 2005. ... Visual Studio uses MSBuild to build and publish ClickOnce ... Fortunately, there's a AfterCompile target, which is built after the ... building and publishing within VS and what's important is that you can see ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Partitioned Single Solution Model
    ... I'm not sure what you mean by "wait for MSBuild". ... for both Visual Studio 2005 and the Build part of Team System. ... Im doing Partitioned Single Solutions. ... >> You are perfectly correct. ...
    (microsoft.public.vstudio.sourcesafe)
  • Re: Working With WPF in D2007/D2008?
    ... Maybe I'm being too persnickety but in the vernacular of both MSBuild and Visual Studio they are referred to as "Project" files. ... While Oxygene has this one; ... And this line is totally uninteresting for Blend. ...
    (borland.public.delphi.non-technical)