ActiveX Software for Visual Basic 6/.NET, C++ 6/.NET, Delphi, Borland C++ Builder: Matrix Maths, Time Series
 
 Home   |   Products   |   Testimonials   |   Prices   |   Support   |   Contact   |   Publications   |   About   |   Buy Now
Quick Links   Home   Purchase   Support   Site Map
Products   Product Home   ActiveX/COM Components   .NET Components   .NETcf Components   Applications   Version History
Support   Support Home   FAQ   Purchase Info   Installation Help   Support Request
About Us   Company Info   Clients   Testimonials   Press Room   Reseller Info   Affiliates   Publications   Contact Us
 
   FAQ - Frequently Asked Questions
 

FAQ Home | Ask A Question FAQ Home | Ask A Question
Can we upgrade from the professional to the enterprise version without any code changes ?

Yes, you can easily upgrade as there are no differences in the method names, property names and so on which could cause a problem in the code itself. However there are some issues to be aware of as explained below.

We have found that in some cases .NET does become very particular about the specific component an application is compiled with. Of course this is by design and is meant to be a useful feature of .NET so that different versions of components can co-exist. In these cases, we have found that it can become necessary to re-compile an application with the new version of a component. Another gotcha is to make absolutely sure the old .NET dll file is completely removed when a new one is being used. Windows has a habit of latching on to the version it started with unless it is physically removed.

Visitor Comments
No visitor comments posted. Post a comment
Related Questions
Attachments
No attachments were found.



Search FAQ
 
 
             
[Advanced Search]


Browse by Category
 
 
User Opinions
0% 100% (1 vote)

How would you rate this answer?
Helpful
Not helpful