Re: Thinking Clearly

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

OK, perhaps that was a bad choice of words. But I consider it more .NET
2.1 than .NET 3.0, as it seems to be a set of extra sub-frameworks and
classes to compliment the existing .NET 2.0 ones, rather than a full
replacement of the classes, SDK and compilers.

It hardly bears any resembliance to what I'd call a .NET 2.1 upgrade such as
..NET 1.1 was. The part of .Net 3.0 formerly known as WinFX does build on
..NET 2.0 as explained by the VP of the Microsoft Developer's Group.
http://blogs.msdn.com/somasegar/archive/2006/05/18/601354.aspx
The fact that .NET 2.0 is considered stable enough to not need replacement
as Microsoft builds out their vision of .NET is good news in my book.

I must admit I'm no expert on exactly what .NET 3.0 will entail, but my
understanding (which I'll gladly have corrected, BTW) is that it is a
framework, and not a development tool, upgrade. So I'd be interested in
hearing what you refer to here. Not trying to be argumentative, BTW;
I,m genuinely curious, and a brief Google is being frustratingly
ambiguous. For example :-

Two good places to start are here:
http://www.netfx3.com/
http://www.winfxguide.com/

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

Another database link that might interest you is this:
http://blogs.msdn.com/euanga/archive/2006/05/31/612398.aspx
Microsoft Visual Studio Team Edition for Database Professionals formerly
known as "Data Dude" which integrates into Visual Studio 2005 Professional
edition or greater. It will not work with the VS Express or Standard
editions since they lack certain essential database features necessary for
Data Dude to work.There's lots going on these days that will make DevCo's
job even harder to keep abreast.

This doesn't really tell me whether this is a framework that is going
to require some special design-time support to consume.

The next version of Visual Studio aka Orca is scheduled for sometime next
year but in the meantime one can use the Orca extensions to VS2005 to
consume the new features in WinFX. There is one for WPF and another for the
Work Flow Foundation (WF).

And considering that the compiler version isn't going to change with
the 3.0 release, there doesn't appear to be any new compiler support
required.

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.

This is why ISTM on the surface that Highlander users should be able to
consume .NET 3.0 without an IDE upgrade. After all, it seems the VS
developers are going to be in the same boat.

Nope - maybe the same ocean but not the same boat...

Sure, Microsoft may well impose restrictions on the installation of
things such as the Sparkle designer, meaning it won't install unless VS
is, but that remains to be seen, and they didn't take that approach
with the current .NET SDKs.

The Expression Interactive Designer aka Sparkle will be a commercial product
that does require WinFX to be installed but doesn't require Visual Studio
except they interact via the VS project files. I would assume if DevCo can
make the equivalent project files visible then EID would also interact with
the BDS. What is specific to Visual Studio is it's own designer for WPF aka
Cider which is currently available to VS2005 users thru the Orca extensions.

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.

Up to this point .NET adoption has mostly been driven by developers

Yeah, but for some developers this adoption may also have a positive
flow on effect for their customers, as they would have a more
productive development environment and framework. Delphi developers
don't get the same level of improvement here, as a lot of the
productivity gains that other developers received with migration to
.NET (and the accompanying IDE) we've had for quite a few years.

Sorry, I'm not going to engage in a BDS with VCL vs. Visual Studio with
NET - "my dad can whip you dad" kind of discussion.<g>



.

Relevant Pages

  • Re: How can you drop Winforms support?
    ... designer and Work Flow designer and that the decision to make ... So that means that in MS's official view the CF designers are not hostable because they're not useful for developers? ... How would you, as an application developer, find it useful to be able to host the CF Forms designer that's in Visual Studio. ... Like I said in the message you are responding to, the person to ask is Soma Somasegar the corporate vice president of the Developer Division at Microsoft Corporation. ...
    (borland.public.delphi.non-technical)
  • Re: How to tell VS not to treat a class as a form
    ... How would visual studio which developers want ... the form to render in the designer and which developers don't. ...
    (microsoft.public.dotnet.framework.windowsforms)
  • Re: What I saw at MS Launch
    ... > developers this frightened away. ... That's a potential weakness that Borland could ... Binding a grid to a collection is now REALLY easy. ... WinForms designer, and have it just display an error message. ...
    (borland.public.delphi.non-technical)
  • Re: Force ClickOnce PreRequisite file to deploy with application?
    ... The ReportViewer.dll that is included with Visual Studio 2005 works fine on my pc, both within Visual Studio 2005, and after deployed, from my pc. ... Assuming that all you really need to install for the user is the dll, you can include it in your deployment package. ... Including the dll in your deployment ensures that if the user installs some other version of that with some other software, it does not cause you any problems, and you don't cause problems with someone else's software either. ... That way, if your developers have different versions of the same software, they will still be running the app and developing against the same version. ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Future of MFC?
    ... MFC could have high-level designer tools ... Don't imagine that we MFC developers like getting our hands dirty when we ...
    (microsoft.public.vc.mfc)