PC Review Forums Newsgroups Microsoft DotNet Microsoft Dot NET Compact Framework ONE DLL for both CompactFramework & FullFramework

Reply

ONE DLL for both CompactFramework & FullFramework

 
Thread Tools Rate Thread
Old 16-01-2006, 08:32 PM   #1
Sal
Guest
 
Posts: n/a
Default ONE DLL for both CompactFramework & FullFramework


Is it possible to create one DLL that will work for both a Pocket PC
App and a regular Windows App? How would I go about doing this?

I wish to create the DLL in either Visual C++ 6.0 or Embedded Visual
C++ 4.0 and use the same DLL in two Visual Studio 2003 Apps (one for
Windows and one for Pocket PC).

Thanks,

Sal

  Reply With Quote
Old 16-01-2006, 08:37 PM   #2
Ilya Tumanov [MS]
Guest
 
Posts: n/a
Default Re: ONE DLL for both CompactFramework & FullFramework

Yes, it is possible. This DLL needs to be managed and created in either C#
or VB.Net with VS 2003 or VS 2005.

If you'd like to use native DLL (which are created with VS 6/eVC 4), you
would need two different DLLs, one for device, one for desktop.

You might be able to share sources for both to some degree.


--
Best regards,

Ilya

This posting is provided "AS IS" with no warranties, and confers no rights.

*** Want to find answers instantly? Here's how... ***

1. Go to
http://groups-beta.google.com/group...framework?hl=en
2. Type your question in the text box near "Search this group" button.
3. Hit "Search this group" button.
4. Read answer(s).

"Sal" <6d3.capstone@gmail.com> wrote in message
news:1137443531.961830.242380@g43g2000cwa.googlegroups.com...
> Is it possible to create one DLL that will work for both a Pocket PC
> App and a regular Windows App? How would I go about doing this?
>
> I wish to create the DLL in either Visual C++ 6.0 or Embedded Visual
> C++ 4.0 and use the same DLL in two Visual Studio 2003 Apps (one for
> Windows and one for Pocket PC).
>
> Thanks,
>
> Sal
>



  Reply With Quote
Old 16-01-2006, 08:58 PM   #3
Sal
Guest
 
Posts: n/a
Default Re: ONE DLL for both CompactFramework & FullFramework

Thanks,

I actually found an article that explains source code sharing.

http://www.danielmoth.com/Blog/2004...llframe_17.html

As long as I can edit one set of source file(s) for both then I'm
happy, which it looks like source code sharing will allow for... at
least I have a solution for now. I'm using native Windows API
functions so I'd prefer make the DLL in VS6/eVC for now, so I don't
have to bother with messy P/Invokes.

Thanks,

Sal

  Reply With Quote
Reply



Thread Tools
Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off