What architecture-related issues should be considered in upgrading a desktop application?
Language issues. You may need to perform additional manual upgrading to resolve language issues, such as external DLL function declarations or thread safety. This work can include creating or changing classes so that they provide basic API services or synchronization among objects. You can upgrade external declarations to .NET Framework classes and new interface classes. In addition, you may need to add references. Note that Visual Basic .NET components (including UserControls) are not inherently thread-safe. Multiple threads are allowed to access a component simultaneously. As a result, code that is thread safe in Visual Basic 6.0 can be unsafe when it is upgraded to Visual Basic .NET. This change will affect you if you are running your component in a multithreaded environment such as Internet Explorer, Internet Information Services, or COM+.2 In this case, you must include new synchronization mechanisms to ensure thread safety. Form issues. Dynamic data exchange (DDE) and drag-and-dr
Related Questions
- Are there any security advantages to using machine virtualization versus application virtualization for running a virtual desktop?
- What architecture-related issues should be considered in upgrading a desktop application?
- How do I know that the Agilent Anytime desktop application does not include a virus?
