Converting a VS6.0 project to VS2005

[dududuil]

GM all,
I have a VS 6.0 project (a Chess program) I want to convert to 2005.
I have no idea where to start.

I don't even know why should I do it.

Can anyone point me to a relevent documentation?

Thanks,
Dudu Arbel

[Jochen Kalmbach [MVP]]

Hi dududuil!

I have a VS 6.0 project (a Chess program) I want to convert to 2005.
I have no idea where to start.
Install VS2005?
Open the project with VS2005?
I don't even know why should I do it.

Then why do you want it?

--
Greetings
Jochen

My blog about Win32 and .NET
http://blog.kalmbachnet.de/

[dududuil]

Well, actually I want to learn this new tool. This is where things are going,
aren't they?

"Jochen Kalmbach [MVP]" wrote:

Hi dududuil!

I have a VS 6.0 project (a Chess program) I want to convert to 2005.
I have no idea where to start.

Install VS2005?
Open the project with VS2005?

I don't even know why should I do it.

Then why do you want it?

--
Greetings
Jochen

My blog about Win32 and .NET
http://blog.kalmbachnet.de/

[David Wilkinson]

dududuil wrote:

Well, actually I want to learn this new tool. This is where things are going,
aren't they?

"Jochen Kalmbach [MVP]" wrote:

Hi dududuil!

I have a VS 6.0 project (a Chess program) I want to convert to 2005.
I have no idea where to start.

Install VS2005?
Open the project with VS2005?

I don't even know why should I do it.

Then why do you want it?

--
Greetings
Jochen

My blog about Win32 and .NET
http://blog.kalmbachnet.de/

dududuil:

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?

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.

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). But once you have done this, you cannot go back, so it is
something to consider very very carefully.

David Wilkinson

[Michael Viking]

"David Wilkinson" <no******@effisols.com> wrote in message
news:OW****************@TK2MSFTNGP15.phx.gbl...

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

[Dave]

On Tue, 6 Dec 2005 15:32:56 -0800, "Michael Viking"
<Th*******@sweden.se> wrote:

"David Wilkinson" <no******@effisols.com> wrote in message

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

Unfortunately it's got pro-Microsoft developers running in circles.
The non-Microsoft companies are using Linux and Java (probably have
their own set of problems).

The state of Windows development had to change. I love the new IDE,
C# and the *concepts* of .NET, but in practice they have proven
troublesome.

The original poster probably doesn't have much new stuff to work on in
C++ until C++/CLI is mainstream. I do wish someone would get a book
published. At that, much of it is designed to get to Win32 code,
which is where he is now.

A more worthwhile thing may be to learn C# and study design patterns.
That way, he may get a better grounding in structure and have a leg up
on Java if he needs it.
I've written 4 chess programs so far
That's impressive. Where did you find out how to do that?
Customers will demand ".NET"
code, believing all the marketing hype, and force mom and pop to jump
through hoops to make their software saleable.

I'm not convinced that end users care whether it says .NET on the
label. I think developers have been sold by a combination of
desirable features and hype, but I'm not ready to go back to Win32 and
VC6 just yet. Too many cool things in VS now. OK, so they're buggy
<g>.

The thing that I find surprising is that MS evidently didn't test
native apps generated by VS2005 (the other thread that you already
commented on).

You'd think that MS would have foreseen the deployment nightmare
caused by their new DLL versioning scheme. They need to divert some
effort from new features and get the old ones to work.

[Michael Viking]

"Dave" <Da**@noemail.com> wrote in message
news:8r********************************@4ax.com...

On Tue, 6 Dec 2005 15:32:56 -0800, "Michael Viking"
<Th*******@sweden.se> wrote:
<SNIP>

I've written 4 chess programs so far
That's impressive. Where did you find out how to do that?

The first one began on a bet while we were talking about chess (I'm a fairly
serious player) and a coworker said "it would be easy to write one I could
do it in a weekend". The bet was on and immediately turned into "we have
one weekend and we'll see whose chess program beats the other - just using
ascii input/output - no researching anywhere; strictly on our own". After
that, I just threw mine (aptly dubbed "Strategery" by my coworker) away and
wrote a new one. Then I researched a lot on the web, threw it away and
wrote a new one. Then bought some books, threw it away and wrote a new one.
Each one is much better than the previous one, and each time I gain more
respect for the professional engines...I've just concentrated on the engine,
some day I'll write one that references an opening book, endgame tablebases,
and uses the Fritz GUI.

Customers will demand ".NET"
code, believing all the marketing hype, and force mom and pop to jump
through hoops to make their software saleable.

I'm not convinced that end users care whether it says .NET on the
label.

We've already had one major customer asking all kinds of pointed questions
about "Is your stuff managed code", "Is it verifiable", etc., etc. Time
will tell.

-Michael Viking