Seeking migration advice

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Joseph Geretz (jgeretz_at_nospam.com)
Date: 03/05/04 

Date: Thu, 4 Mar 2004 21:27:50 -0500

I don't know if this is the right group for my question, but I'm seeking
advice from knowledgable .NET developers. Hopefully I've come to the right
place.

I work with a document management application which is tightly integrated
with the workstation Windows environment. Our software does not necessarily
handle any specific document type. User's can import any document type into
our repository. On the display side, we use WinAPI to discover the
associated application for a particular file type, and then to launch that
document with its associated application. To make matters even more
seamless, the native application is embedded into our own application
desktop space, again, using the WinAPI. I can safely say that this
particular VB application is more dependent on WinAPI than any other VB
application I have worked with.

We are contemplating a move to .NET, and a conversion of our Client / Server
architecture to n-Tier. The server side tier will definitely be implemented
using .NET Web Services. Given our dependency on Win32 at the client though,
I'm wrestling with whether the Framework environment at the client will
allow me the close integration we need with the Windows environment and with
the applications registered in that environment, to do the sort of API
operations I've described above. Although I've done several front-to-back
n-tier implementations in .NET, none of them have had this sort of
dependency on Win32 at the client, so I don't really have any frame of
reference to make this determination. Has anyone out there done .NET
implementations with heavy dependency on Win32 API?

Thanks for any advice which you can offer.

- Joe Geretz -

Relevant Pages

  • Seeking migration advice
    ... with the workstation Windows environment. ... User's can import any document type into ... We are contemplating a move to .NET, and a conversion of our Client / Server ... Given our dependency on Win32 at the client though, ...
    (microsoft.public.dotnet.languages.csharp)
  • Seeking migration advice
    ... with the workstation Windows environment. ... User's can import any document type into ... We are contemplating a move to .NET, and a conversion of our Client / Server ... Given our dependency on Win32 at the client though, ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Seeking migration advice
    ... > with the workstation Windows environment. ... > handle any specific document type. ... we use WinAPI to discover the ... > implementations with heavy dependency on Win32 API? ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Seeking migration advice
    ... > with the workstation Windows environment. ... > handle any specific document type. ... we use WinAPI to discover the ... > implementations with heavy dependency on Win32 API? ...
    (microsoft.public.dotnet.framework.windowsforms)
  • Re: Abstract public member variales?
    ... In functional decomposition the SRS gives the requirements for the one main function that is above all others and represents the entire software. ... In the OO paradigm the one has two quite different views of 'client'. ... Sine the OO paradigm uses problem space abstraction to organize groups of requirements by objects and responsibilities independently, there is no hierarchy and inherent dependency chain in the resolution of requirements. ... You seem to be talking about a situation in which the client specifies every operation of Benefit3, including the database accesses and every formula used. ...
    (comp.object)