|
-
Aug 27th, 2002, 03:58 PM
#1
Thread Starter
Frenzied Member
ok vc++ 7 question
I want to upgrade an old style dll that exports about 15 methods to a new style .net assembly dll. the question I have is there is all this talk about not sing api in .net and blah blah blah the old dll is a big api wrapper more or less and well if i convert the thing i will still be using the api. is that bad..?
Magiaus
If I helped give me some points.
-
Aug 27th, 2002, 07:08 PM
#2
Thread Starter
Frenzied Member
i don't think it can be that bad to because MS has to either be calling the api from the .net framework or they did a rewrite of the api and placed it in the framework...? any thoughts?
Magiaus
If I helped give me some points.
-
Aug 28th, 2002, 05:34 AM
#3
The .NET framework does API calls, just like everything else windows. The idea is that ONLY the framework does API calls, and neither apps nor dlls do it.
You may want to rewrite your dll so that it uses the .NET framework, or maybe the things that you dll does are already done somewhere in the framework (it's HUGE).
All the buzzt
 CornedBee
"Writing specifications is like writing a novel. Writing code is like writing poetry."
- Anonymous, published by Raymond Chen
Don't PM me with your problems, I scan most of the forums daily. If you do PM me, I will not answer your question.
-
Aug 28th, 2002, 10:18 AM
#4
Thread Starter
Frenzied Member
ok thats what i figured
thanks cornedbee
Magiaus
If I helped give me some points.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|