Maybe a stupid question about .NET and 6.0

Hi!

I'm developing a DLL with Visual C++ 6.0.
I would like that DLL could be used later for developing programs in Visual C++ .NET.

I think there shouldn't be any problem... or am I wrong?

Thank you in advance.

Whoa! Even Irona is jumping onto the .Net bandwagon and trying to keep up with the times! :)

No no....basically, you can't assume anything. I got a friend who migrated code from Visual C++ 6 to .net and he got lottsa compile errors. It all depends, really. Thus, girl....you can't make any assumptions. :D:D:D:D:D

From what i can gather you can end up getting lots and lots of annoying warnings but usually not many serious errors.

For example M$ have decided that all collection classes (ie CArray, CPtrArray etc) now return INT_PTR data types instead of int. Just means you have to typecast everything into integers to remove the warnings.

Maybe this is due to the error warning level, im not sure, ive not actually had time to locate where the level can be changed in .NET

zebbedi

Ok, thank you very much. I will see what happens when I get Visual C++ .NET :)

Thank you again.

Irona, If your v6.0 code really follows the rules and does not exploit some of the "loopholes" that V6.0 allows the converyion to UNMANAGED C++ 7.0 should be fairly painless.

If you code in a style of "Hey I know I can get away with this, I've done it before and it worked", then V7.0 can be a nightmare.

Hope this helps

Thanks for your answer TheCPUWizard.

My DLL basically uses CORBA functions (using the IDLs), so I hope don't have any problem :)

Seriously, though.....Irona....you better get some hair dye(to color your hair brown) and some mental pills and medicine before you compile your project in Visual C++ .net.

Some sleeping pills would be nice too, cos' you can have nightmares at night of the Visual C++ .net compiler and linker giving you the strangest errors and bugs ever.
(for example, you run your program, click a push-button and the entire Windows OS fail to start-up the next time you run boot the computer up)

Need I say more?! :cool::cool::cool::cool::D

Quote:

---

Originally posted by Xeon
Seriously, though.....Irona....you better get some hair dye(to color your hair brown) and some mental pills and medicine before you compile your project in Visual C++ .net.

---

I don't want to compile my project, I only want to use my DLL :)

PS: Need I say more? (tm) :p

From Irona:

Quote:

---

I don't want to compile my project, I only want to use my DLL

---

This is even worse!!!!!! :eek::eek:
DLL??!!! This is what programmers call "DLL He||"!!!!! :eek:

Errr.....Irona...prepare to get a hammer to smash your PC and VS.net. :cool:

Quote:

---

PS: Need I say more? (tm)

---

[/quote]

Drats! How dare you use my line without my permission!!!! Gggrrrr....ok. Never mind. Hypnotise yourself and gimme everything you have.(except your boyfriend :D)

Dll **** is when different programs overwrite common windows .dll with thier own version. This causes problems on Windows 9x and NT, because sometimes the different .dlls are not compatible and the programs that use will crash. Windows 2000 and XP keep separate version of each different .dll for the programs that use them, so this problem can not occur.

If you ever used Windows NT, you would remember having to re-apply the service packs every time you installed a driver or new software because the software would over-write the service pack .dll with an older/different version. Oh how I hated NT :)