Board index » delphi » Suggestions required about D7-> Turbo Delphi for win32 migration

Suggestions required about D7-> Turbo Delphi for win32 migration


2006-09-13 07:08:44 PM
delphi7
Hi all
i currently use Delphi 7 Pro.
1) with reference to Win32 programming only (for .NET i have already
switched to VC# 2005 Express) which benefits could I get installing the new
Turbo Delphi for win32 (free edition)?
2) Are there some problems installing it, considering that i have already
VC# 2005 Express/NET 2.0 and for example in the TD "prereqs" I have read
Microsoft.NET 1.1 runtime and SDK.
3) In the free edition i know it is not allowed to install 3rd part
components in the IDE palette: is this true also for, say, self-made
components, I mean for components selfdeveloped?
thanks in advance for any suggestion/help about the above!
 
 

Re:Suggestions required about D7-> Turbo Delphi for win32 migration

"Joey" <XXXX@XXXXX.COM>writes
Quote
1) with reference to Win32 programming only (for .NET i have already
switched to VC# 2005 Express) which benefits could I get installing the
new Turbo Delphi for win32 (free edition)?
If you currently use Delphi 7 Pro, and we're talking *purely* about Win32
development, then your benefits in moving to the free edition of Turbo
Delphi/Win32 would be minimal. Any gains in moving to a more recent product
would be more than offset by the inconvenience of not being able to install
third-party components.
Quote
2) Are there some problems installing it, considering that i have already
VC# 2005 Express/NET 2.0 and for example in the TD "prereqs" I have read
Microsoft.NET 1.1 runtime and SDK.
If you're running VC# 2005 Express, then you've obviously got .NET 2.0
installed. Unfortunately, Turbo Delphi requires .NET 1.x. In my
experience, trying to install .NET 1.x when .NET 2.0 is already installed
has a good chance of screwing up your existing .NET 2.0 config.
Quote
3) In the free edition i know it is not allowed to install 3rd part
components in the IDE palette: is this true also for, say, self-made
components, I mean for components selfdeveloped?
As has already been discussed in this group, it is perfectly ok to install
your own components as long as you put them in the DCLUSR package.
Bottom line: from the sounds of it, you'd be better sticking with Delphi 7 Pro
unless you intend to buy Turbo Delphi Pro.
Dave
 

Re:Suggestions required about D7-> Turbo Delphi for win32 migration

Dave Jewell <XXXX@XXXXX.COM>writes
<XXXX@XXXXX.COM>
Quote
In my
experience, trying to install .NET 1.x when .NET 2.0 is already installed
has a good chance of screwing up your existing .NET 2.0 config.
Then .NET has done nothing to solve "DLL hell".
--
***Free Your Mind***
Posted with JSNewsreader Preview 0.9.4.2779
 

Re:Suggestions required about D7-> Turbo Delphi for win32 migration

"Joey" <XXXX@XXXXX.COM>writes
Quote
Hi all
Hola!
Quote
i currently use Delphi 7 Pro.

1) with reference to Win32 programming only (for .NET i have already
switched to VC# 2005 Express) which benefits could I get installing the
new Turbo Delphi for win32 (free edition)?
Advantages WIN32 wise, between Delphi 7 and D2006, lets see, first, a great
new memory manager, if you are not using FastMM, then you will feel right in
the spot
a great performance difference. Inline statements, which can also improved
performance... oh, lots of RTL functions using faster implementations thanks
to the FastCode planning.
IDE:
Wow, differences in the IDE between Visual S and the Delphi one, simply, you
will love it, first it may shock you with the toolbar location, but after
that, the code templates, the hotkeys to access the component pallete, the
syncedit, the refactoring options (lots more and more complex than Visual
S), there are lots of articles going through all this options, so just
google a bit and you will see it.
Quote
2) Are there some problems installing it, considering that i have already
VC# 2005 Express/NET 2.0 and for example in the TD "prereqs" I have read
Microsoft.NET 1.1 runtime and SDK.

It uses SDK 1.1 for .Net development, and it is required by the Delphi IDE.
Im using BDS, having also VS 2005 installed with no problem at all.
Quote
3) In the free edition i know it is not allowed to install 3rd part
components in the IDE palette: is this true also for, say, self-made
components, I mean for components selfdeveloped?

thanks in advance for any suggestion/help about the above!

Can't help you on the last one, but i think that selfdeveloped components
are allowed.
Cya.
Esteban Pacheco
A Delphi Programming Blog
estebanp.blogspot.com
 

Re:Suggestions required about D7-> Turbo Delphi for win32 migration

Quote
Then .NET has done nothing to solve "DLL hell".
Wrong, DLL hell has been solved (somehow... if you don't look to close).
You're now presented with three brand new hells:
- HKEY_CLASSES_ROOT hell
- GAC hell
- MSI hell
Eric
 

Re:Suggestions required about D7-> Turbo Delphi for win32 migration

Quote

Then .NET has done nothing to solve "DLL hell".

I believe it has gotten worse, if you are mixing managed and native and
exposing .NET assemblies via a CCW. If you are not really careful, it is way
too easy to mess up the registry.
More than one assembly version can have the same GUID.
 

Re:Suggestions required about D7-> Turbo Delphi for win32 migration

"John Jacobson" <jake@j[nospam]snewsreader.com>writes
Quote
Dave Jewell <XXXX@XXXXX.COM>writes
<XXXX@XXXXX.COM>
>In my
>experience, trying to install .NET 1.x when .NET 2.0 is already installed
>has a good chance of screwing up your existing .NET 2.0 config.

Then .NET has done nothing to solve "DLL hell".
.Net has solved DLL hell. it is now called "Assembly hell". Giving it a
new name makes the old problem go away.
:)
krf
 

Re:Suggestions required about D7-> Turbo Delphi for win32 migration

At first I didn't understand the acronym, but then I found a whole website
about GAC hell:
www.gactv.com/
--Dag--
"Eric Grange" <XXXX@XXXXX.COM>writes
Quote
>Then .NET has done nothing to solve "DLL hell".

Wrong, DLL hell has been solved (somehow... if you don't look to close).

You're now presented with three brand new hells:
- HKEY_CLASSES_ROOT hell
- GAC hell
- MSI hell

Eric
 

Re:Suggestions required about D7-> Turbo Delphi for win32 migration

Kevin Frevert writes:
Quote
>Then .NET has done nothing to solve "DLL hell".

.Net has solved DLL hell. it is now called "Assembly hell".
Giving it a new name makes the old problem go away. :)
No, but developing in .Net makes it vanish.
I am utterly satisfied with .Net with respect to this.
--
Ingvar Nilsen
www.ingvarius.com
 

Re:Suggestions required about D7-> Turbo Delphi for win32 migration

Quote
>Then .NET has done nothing to solve "DLL hell".

Wrong, DLL hell has been solved (somehow... if you don't look to close).

You're now presented with three brand new hells:
- HKEY_CLASSES_ROOT hell
- GAC hell
- MSI hell

It's what I have always suggested, they didn't really solve anything, they
just shifted the problems around. But to give them the benefit of the doubt,
I'm not sure if it is a problem that *can* be solved, regarding the nature of
the beast...
-BKN
 

Re:Suggestions required about D7-> Turbo Delphi for win32 migration

Quote
IDE:
Wow, differences in the IDE between Visual S and the Delphi one, simply,
you will love it, first it may shock you with the toolbar location, but
after that, the code templates, the hotkeys to access the component
pallete, the syncedit, the refactoring options (lots more and more complex
than Visual S), there are lots of articles going through all this options,
so just google a bit and you will see it.

I just wish they would address the niggling bugs in the floating/classic
IDE...
(and I still miss the Component Palette).
-BKN
 

Re:Suggestions required about D7-> Turbo Delphi for win32 migration

Quote
i currently use Delphi 7 Pro.

Need I say again, another non-BDS user contemplating "upgrading" to Turbo
(and not to BDS)?
-BKN
 

Re:Suggestions required about D7-> Turbo Delphi for win32 migration

In article <45081a1e$XXXX@XXXXX.COM>, Eric Grange says...
Quote
>Then .NET has done nothing to solve "DLL hell".

Wrong, DLL hell has been solved (somehow... if you don't look to close).

You're now presented with three brand new hells:
- HKEY_CLASSES_ROOT hell
- GAC hell
- MSI hell
Sounds like Dante.net to me!
lol
--
Jolyon Smith
 

Re:Suggestions required about D7-> Turbo Delphi for win32 migration

In article <XXXX@XXXXX.COM>, Bryce K. Nielsen says...
Quote
>>Then .NET has done nothing to solve "DLL hell".
>
>Wrong, DLL hell has been solved (somehow... if you don't look to close).
>
>You're now presented with three brand new hells:
>- HKEY_CLASSES_ROOT hell
>- GAC hell
>- MSI hell
>

It's what I have always suggested, they didn't really solve anything, they
just shifted the problems around.
And gave it a new name. The history books on the shelf are _always_
repeating themselves!
(lest we forget, the UAE begat GPF begat AV. Or maybe GPF begat UAE? I
forget. Ooops, lested)
:)
--
Jolyon Smith
 

Re:Suggestions required about D7-> Turbo Delphi for win32 migration

In article <4508385f$XXXX@XXXXX.COM>, Bryce K. Nielsen says...
Quote
>i currently use Delphi 7 Pro.
>

Need I say again, another non-BDS user contemplating "upgrading" to Turbo
(and not to BDS)?
Ssshhhh - we're not supposed to talk about that.
;)
--
Jolyon Smith