|
Check LVN_ITEMCHANGING and LVN_ITEMCHANGED.
Tomasz Sowinski -- http://www.shooltz.com
- It's for protection
- Protection from what? Zee Germans?
|
|
|
|
|
|
|
Hi,
I created a setup using the a setup project in Visual C++ .NET Standard, which works absolutely fine on the dev box, but when I try a vanilla install of Windows 2000 it complains saying it needs the .NET framework installed.
Surely MS Installer 2.0 doesn't need the .NET framework?!
Any help very gratefully received.
TIA.
Paul.
|
|
|
|
|
PaulMdx wrote:
Surely MS Installer 2.0 doesn't need the .NET framework?!
Maybe not, but perhaps your program does!
Nish
Regards,
Nish
Native CPian.
Born and brought up on CP.
With the CP blood in him.
|
|
|
|
|
Hi Nish,
Thanks for the reply.
Nope, that's not it. We also tried adding the .NET framework MSM, which didn't do anything.
The setup complains before the program is even installed (when the setup.exe is first clicked on).
Paul.
|
|
|
|
|
Hmmm.
This is a wild guess, okay! But in most installers we can set the option to check for some bare minimums. For example you can set the minimum requirements to Windows 98 or say you can insist on IE 5.5 etc...
Maybe somewhere in your installation settings you have enabled the .NET runtime requirement. Thus the installer sees that the runtime is not installed and it stops!
If this was a stupid guess, please forgive me. I am just making a long shot in the dark.
Nish
Regards,
Nish
Native CPian.
Born and brought up on CP.
With the CP blood in him.
|
|
|
|
|
|
As a long time C++ programmer, I find VC++ far superior to Delphi for the kind of work I do.
Delphi is a little too focused on RAD for my way of developing.
Michael 
Errata 1: p. 154, section 'Defusing'. For 'red wire' read 'blue wire'.
|
|
|
|
|
choosing either Delphi or Visual C++ depends largely on what you are doing.... although C++ executes faster, Delphi compiles in a single pass which means it will always be faster than MSVC, and most other C/C++ compiler out there.... Delphi is also based on the Pascal language, but borland have their own version, Object Pascal, which supports most features found in C++
if you want to do database programming, or large GUI-based programs (using windows common controls and such), Delphi is by far the best choice. if you plan on creating games or other performance-critical applications, C++ is probably a better choice (i am not saying Delphi is slow in any way here, because it isnt). if you want to learn programming, Delphi is far easier to learn than Visual Basic and outperforms it in just about any circumstance (Delphi executables also dont need a DLL with the runtime libraries in it to run either, but that option can be activated to produce tiny executables....)
I actually have both Visual C++ and Delphi and use them both often - which one you use depends on what you want to do (although i prefer Delphi for it's ease of use....)
in the end, it's up to you....
(sorry for the massive amount of text, but im going through caffeine withdrawal and my brain is going crazy....
-- señor codeman
codeman@crowbartherapy.cjb.net
|
|
|
|
|
East or West NoDoubt.. VC++ is best..
Renjith The True CP ian
|
|
|
|
|
We do database applications and large GUI based programs, but we use VC++ because we can make very small distribution packages which is critical for us as we do all business via the internet so our clients must download the program as we do not send any software on CD.
I don't know anything about Delphi, but I'm thinking on difference might be that a setup for a Delphi built business application versus a C++ built one would be much larger.
Is that the case?
|
|
|
|
|
No. MFC apps are generally much larger than Delphi apps. If you want small C++ apps, use WTL.
|
|
|
|
|
i'm not exactly sure which produces smaller exe's, but delphi can create standalone versions which don't rely on msvcrt.dll or similar libraries, or a library-dependant version (which chops a lot off the output file's size, but then it needs the runtime library dll, standalone versions only link with parts they need so they're usually smaller and simpler when installing on an end-user system.... the library dependant version rocks for development because it size is comparable to MSVC, Borland C++ and even, dare i say it, VB. smaller files means i have more hard drive space, which is an issue for me at the moment, being a 'poor student'......
personally i think the output file size difference wouldn't be worth comparing - Delphi was designed to develop business applications quickly (how many games were written in Delphi? not many compared to Visual C++) and it does that task well. from a beginner's point of view, its also a lot easier to learn and use (i learnt it first) - C++ has a bit more power than Delphi, but i've never needed any features that C++ has and Delphi doesn't. once again i guess it comes down to personal choice and experience...
btw, i'm only 17 years old (last year of high school in australia), so i dont have much experience writing business apps - if anyone from melbourne/geelong area wants to change that you have my email address... 
-- señor codeman
codeman@delphidudes.com
|
|
|
|
|
VC++
Nish
p.s. Never used Delphi!
Regards,
Nish
Native CPian.
Born and brought up on CP.
With the CP blood in him.
|
|
|
|
|
Nish - Native CPian wrote:
p.s. Never used Delphi!
You wouldn't like it. Think of it as Visual Basic for PASCAL programmers
Michael
Errata 1: p. 154, section 'Defusing'. For 'red wire' read 'blue wire'.
|
|
|
|
|
That is not true! Delphi is OOP designed, has classes, inheritance and exceptions, and VCL si a GUI class library similar to MFC. You cannot say the same thing about vb
Best regards,
Alexandru Savescu
|
|
|
|
|
It was a joke!
Although the original Delphi was very close to what I said. However it has evolved very nicely but is still too GUI centered for my tastes.
Michael
Errata 1: p. 154, section 'Defusing'. For 'red wire' read 'blue wire'.
|
|
|
|
|
Okay. Let's say Delphi would come somewhere in between VB 6 and VB.NET
That's a fair compromise I guess
Nish
Regards,
Nish
Native CPian.
Born and brought up on CP.
With the CP blood in him.
|
|
|
|
|
Nish - Native CPian wrote:
Okay. Let's say Delphi would come somewhere in between VB 6 and VB.NET
ROFLMAO
Michael
Errata 1: p. 154, section 'Defusing'. For 'red wire' read 'blue wire'.
|
|
|
|
|
Ok, I get it, but why do you want to mock at Nish by telling him lies?
Best regards,
Alexandru Savescu
|
|
|
|
|
I had the misfortune to write a Delphi based app a few years back - I always hated the fact that you had to explicitly call class constructors with Delphi - truly gross.
Free
|
|
|
|
|
Michael P Butler wrote:
Think of it as Visual Basic for PASCAL programmers
That's exactly how I think of it now
Nish
Regards,
Nish
Native CPian.
Born and brought up on CP.
With the CP blood in him.
|
|
|
|
|
exactly, except that Visual Basic is useless compared to Delphi - pointers aren't really supported in VB, it doesn't have inline assembly support, i don't know about 64-bit integers, and classes.... VB almost has those.... oh and Delphi supports them all. being as easy as VB makes it good for when you first learn to code, because bBASIC really isnt good for that (i leanred that about 8 years ago.... been using Delphi for 4 or 5 years and C/C++ for about 3 or 4 years....)
-- señor codeman
codeman@delphidudes.com
|
|
|
|
|
i think delphi is for applications that u have to do them quickly, coz it has a lot of components and that make easier the development. And i like C++ Builder more than Delphi and it has the same components, And is C++
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
