Important Notice from AspDotNetStorefront
It is with dismay that we report that we have been forced, through the action of hackers, to shut off write-access to this forum. We are keen to leave the wealth of material available to you for research. We have opened a new forum from which our community of users can seek help, support and advice from us and from each other. To post a new question to our community, please visit: http://forums.vortx.com
Results 1 to 3 of 3

Thread: Effect of changing from C# to VB

  1. 12-16-2008, 08:37 AM #1
    dhchris is offline Junior Member
    Join Date
    Dec 2008
    Posts
    2

    Default Effect of changing from C# to VB

    Hello,

    We developed an integrated application, written in C#, that interacts with our client's AspDNSF database. Now the client wants to switch from the C# source code to the VB source code as well as upgrade to v8.0. Will either of these changes impact the ability of our integrated application to work with the store's underlying database?

    Thanks,
    Chris
  2. 12-16-2008, 08:44 AM #2
    Jesse is offline Banned
    Join Date
    May 2008
    Posts
    1,329

    Default

    It's very likely. Revisions of the software often times make changes to data structure, sprocs, and other database entities from one version to the next. Depending on how you implemented your third party and how the database is accessed it could very well need reimplemented.
  3. 12-16-2008, 01:33 PM #3
    dhchris is offline Junior Member
    Join Date
    Dec 2008
    Posts
    2

    Default

    As for the versioning, we'd like to write our software so that it can automatically recognize the version of AspDNSF and branch accordingly. Is there any table in the database that tells us which version we're dealing with?

    Thanks,
    Chris