Re: Converting a VS6.0 project to VS2005

"David Wilkinson" <no-reply@xxxxxxxxxxxx> wrote in message
news:OWOy7Np%23FHA.3992@xxxxxxxxxxxxxxxxxxxxxxx
> dududuil wrote:
>
> Maybe all programming on Windows is moving toward the .NET platform. Or
> maybe it isn't. Personally, I see the whole thing as a bit of a mess
> right now. Obsolete managed C++ syntax. Soon to be obsolete WinForms?

It sure seems like a total mess reading the newsgroups. How can the syntax
be obsolete from version to version? It all begins to make sense if you
imagine that it's a devilish scheme cooked up to have non-Microsoft
companies running around in circles, never gaining any traction - while
giving people who making a living training on this stuff something to do.
Meanwhile, MS doesn't get high on its own supply.
>
> But anyway, just compiling your app to VC8 does not move you in this
> direction at all. It just gives you a better compiler, and (in many
> peoples' opinion) a worse IDE. No .NET involved. So you should perhaps
> consider why you are doing it.

I for one think the IDE is very bad compared to VS6, but I imagine this
depends on how hard core an editor you are. I've written 4 chess programs
so far (gotta admire the writers of Shredder, Fritz, etc. wow!) and I don't
really see any reason to do any .NET stuff for chess at all. No way it can
improve performance. Maybe you can get a tiny, slight, imperceptible
improvement in performance due to a better optimizer, but in general, any
improvements will come from better pruning algorithms, etc.

>
> One reason to do it is so you can start to incorporate .NET features in
> your app. This is what MS wants you to do (even though they do not do it
> themselves).

Of course they haven't! Then they'd be treading water like all the other
poor souls who jumped on board instead of moving forward. This is really
going to hurt a lot of companies, I believe. Customers will demand ".NET"
code, believing all the marketing hype, and force mom and pop to jump
through hoops to make their software saleable. Meanwhile MS won't have to
jump through the hoops because they're MS. The same thing happened to a lot
of players with MSI and installer technology and getting a Windows logo. MS
didn't have to certify its apps to be logo compliant, because they're
MS...but we sure did, and it cost (and costs) a lot of resources.

-Michael Viking


.

Relevant Pages

  • Re: Confusing stack effects
    ... And DOS ... is the best way to start assembly programming. ... To learn todo 16-bit dos programming, for programming in windows later is the worst kind of advice. ... Learning to program for a Click&Go GUI is a tedious incredible complex job, compared to doing a dos app, where all you need to do is set up a loop, to take input that in all cases _you_ made the rules for. ...
    (alt.lang.asm)
  • Re: Is VS2008 a good environment?
    ... Upon programming VS2008 using win32 and C++, I find that it is not ... Every windows app needs to process messages, ... Which takes care of the "Make Windows programming OOP" ...
    (microsoft.public.win32.programmer.ui)
  • Re: Windows Forms Application
    ... #Windows Forms Programming in C# ... how to reference objects not in the current form? ... functionality in your app. ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.
    ... app works perfectly on Windows 2000 server, but after moving same app to ... I am running my app on HP DL380 server, on a HP ProCurve switched network, ...
    (microsoft.public.inetserver.asp.general)
  • Re: [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.
    ... app works perfectly on Windows 2000 server, but after moving same app to ... I am running my app on HP DL380 server, on a HP ProCurve switched network, ...
    (microsoft.public.sqlserver.programming)
Loading