Advice needed...

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • jmar

    #1

    Advice needed...

    NOTE: the following has been posted in
    microsoft.publi c.vb.general.di scussion and they have recommended I
    also post here.

    Let me apologize up front about the length of this post, but I want to
    get opinions and I need to provide some background...

    In the 90's, I worked as an independent contractor and designed a set
    of customized quote generation programs (4 total, one for each product
    line) for a client in VB4.0 16 bit using Access databases. Basically
    the user enters customer information, application information and
    specifies model parameters if desired and the program goes through a
    bunch of engineering calculations to select the best model for the
    application. At that point the user can select options/accessories
    and a quote is generated in either Crystal Report format or MS Word
    format.

    I can't claim to be a great coder, but I managed to teach myself
    enough to get the job done - probably not very efficiently :) These
    programs are distributed world-wide to their reps and therefore used
    on new/old computers and a range of operating systems. Over the years
    we worked out any bugs/issues as they popped up and the programs were
    quite reliable.

    Around 2001, I pursued a lifelong dream of becoming a teacher and cut
    back my programming hours considerably (8-12 week). After spending a
    year or two maintaining the programs, working on other projects
    (website, etc) and dabbling with the thought of converting them to
    VB6.0, we decided to wait for VB.net 2003. Once that came out we
    started the process of converting them. Much to my frustration, it
    wasn't nearly as simple as Microsoft made it sound and the learning
    curve was STEEP. It didn't help that every time I started to make
    substantial headway, I would be sidetracked by other projects for the
    client. Not a very efficient way to learn a language. In the
    meantime, every year I would update the pricing in the databases and
    send out the VB4.0 programs via CD. I've basically updated only one
    of the four programs to VB.net at this point because everytime I take
    two steps forward, I get sidetracked for a long period of time and
    then have to figure things out again.

    Here's where I need your thoughts/input. Over the last year or two
    I've spoken openly with my client about the inefficiencies of this
    arrangement and about my concerns with the potential of the programs
    not to work properly anymore. With Windows Vista, I think we may have
    run into this issue head-on.

    Two weeks ago, a rep bought a machine with Vista Ultimate. He
    installed my application programs and we have discovered that any
    labels that were placed on either the SSPanel or SSFrame controls
    don't show up at all - they are basically invisible. Labels on the
    standard panel or frame controls work perfectly. Even more
    interesting is that I asked the rep to walk through the entire quote
    generation process and his initial report is that it seems to work
    fine except the missing labels (I was very surprised to hear that)

    1) Does anyone have any idea what might cause this issue and how I
    can fix it? The easy answer is to convert to standard controls but
    before I go about that (there are a lot of forms using SS controls), I
    thought maybe there was an easier way. Especially because I use the
    SSTab control and that won't be easy to replace in my layout.

    Any help would be appreciated. Of even greater interest is your
    opinions on the next topic. While trying to find out a bit about Vista
    compatibility, I came across an article which indicates the VB.net
    2003 and even VB.net 2005 may not be fully supported by Vista (http://
    https://www.theserverside.net/news/t...read_id=42426). This really
    surprised me and led to a discussion that I need your opinions on.

    2) My client initially wants to just get the programs so they can be
    installed on a Vista machine. Can I do this with VB4.0 16 bit
    programs or am I going to be looking at a ton of other issues?

    3) After we get them at least functioning on Vista, we want to
    obviously upgrade them. What's the best route to go? We have to
    decide what programming environment to invest our time/energy in. The
    link above makes me question continuing on the VB.net journey (which I
    haven't even looked at in 4 months because of other projects). There
    has long been a thought of making them web-based to greatly simplify
    distribution/updgrades,etc. One of the potential negatives would be
    the requirement for internet access (often the reps are traveling
    pretty remotely) and/or speed of internet access. What helps you
    decide to go web-based vs stand-alone application? What positives/
    negatives should I be aware of?

    If we send them out as a stand-alone application, what language should
    we consider developing them in? Obviously we don't want to go down a
    road that ends up being a dead end in the near future.

    Unfortunately with my limited hours, I haven't been able to keep up on
    the trends in programming. I'm trying to get a feel of what avenues I
    should explore. In advance, let me thank anyone who provides a bit of
    insight into this murky situation.

    Sincerely,


    Jmar


    P.S. Please don't go into a discussion about how the client should
    spend more money or hire someone full-time, etc. Budget constraints
    have dictated many of their decisions and will continue to do so. The
    programs have been sufficient to get by with and many of their reps
    are behind when it comes to technology and the latest hardware/
    software.

  • Tom Leylan

    #2
    Re: Advice needed...

    There is another option which buy you some time... consider Virtual PC (from
    Microsoft) you can't beat the price (free).

    http://www.microsoft.com/windows/pro...mily/virtualpc


    "jmar" <jmarzion@yahoo .comwrote in message
    news:1179713949 .084335.286330@ b40g2000prd.goo glegroups.com.. .
    NOTE: the following has been posted in
    microsoft.publi c.vb.general.di scussion and they have recommended I
    also post here.
    >
    Let me apologize up front about the length of this post, but I want to
    get opinions and I need to provide some background...
    >
    In the 90's, I worked as an independent contractor and designed a set
    of customized quote generation programs (4 total, one for each product
    line) for a client in VB4.0 16 bit using Access databases. Basically
    the user enters customer information, application information and
    specifies model parameters if desired and the program goes through a
    bunch of engineering calculations to select the best model for the
    application. At that point the user can select options/accessories
    and a quote is generated in either Crystal Report format or MS Word
    format.
    >
    I can't claim to be a great coder, but I managed to teach myself
    enough to get the job done - probably not very efficiently :) These
    programs are distributed world-wide to their reps and therefore used
    on new/old computers and a range of operating systems. Over the years
    we worked out any bugs/issues as they popped up and the programs were
    quite reliable.
    >
    Around 2001, I pursued a lifelong dream of becoming a teacher and cut
    back my programming hours considerably (8-12 week). After spending a
    year or two maintaining the programs, working on other projects
    (website, etc) and dabbling with the thought of converting them to
    VB6.0, we decided to wait for VB.net 2003. Once that came out we
    started the process of converting them. Much to my frustration, it
    wasn't nearly as simple as Microsoft made it sound and the learning
    curve was STEEP. It didn't help that every time I started to make
    substantial headway, I would be sidetracked by other projects for the
    client. Not a very efficient way to learn a language. In the
    meantime, every year I would update the pricing in the databases and
    send out the VB4.0 programs via CD. I've basically updated only one
    of the four programs to VB.net at this point because everytime I take
    two steps forward, I get sidetracked for a long period of time and
    then have to figure things out again.
    >
    Here's where I need your thoughts/input. Over the last year or two
    I've spoken openly with my client about the inefficiencies of this
    arrangement and about my concerns with the potential of the programs
    not to work properly anymore. With Windows Vista, I think we may have
    run into this issue head-on.
    >
    Two weeks ago, a rep bought a machine with Vista Ultimate. He
    installed my application programs and we have discovered that any
    labels that were placed on either the SSPanel or SSFrame controls
    don't show up at all - they are basically invisible. Labels on the
    standard panel or frame controls work perfectly. Even more
    interesting is that I asked the rep to walk through the entire quote
    generation process and his initial report is that it seems to work
    fine except the missing labels (I was very surprised to hear that)
    >
    1) Does anyone have any idea what might cause this issue and how I
    can fix it? The easy answer is to convert to standard controls but
    before I go about that (there are a lot of forms using SS controls), I
    thought maybe there was an easier way. Especially because I use the
    SSTab control and that won't be easy to replace in my layout.
    >
    Any help would be appreciated. Of even greater interest is your
    opinions on the next topic. While trying to find out a bit about Vista
    compatibility, I came across an article which indicates the VB.net
    2003 and even VB.net 2005 may not be fully supported by Vista (http://
    https://www.theserverside.net/news/t...read_id=42426). This really
    surprised me and led to a discussion that I need your opinions on.
    >
    2) My client initially wants to just get the programs so they can be
    installed on a Vista machine. Can I do this with VB4.0 16 bit
    programs or am I going to be looking at a ton of other issues?
    >
    3) After we get them at least functioning on Vista, we want to
    obviously upgrade them. What's the best route to go? We have to
    decide what programming environment to invest our time/energy in. The
    link above makes me question continuing on the VB.net journey (which I
    haven't even looked at in 4 months because of other projects). There
    has long been a thought of making them web-based to greatly simplify
    distribution/updgrades,etc. One of the potential negatives would be
    the requirement for internet access (often the reps are traveling
    pretty remotely) and/or speed of internet access. What helps you
    decide to go web-based vs stand-alone application? What positives/
    negatives should I be aware of?
    >
    If we send them out as a stand-alone application, what language should
    we consider developing them in? Obviously we don't want to go down a
    road that ends up being a dead end in the near future.
    >
    Unfortunately with my limited hours, I haven't been able to keep up on
    the trends in programming. I'm trying to get a feel of what avenues I
    should explore. In advance, let me thank anyone who provides a bit of
    insight into this murky situation.
    >
    Sincerely,
    >
    >
    Jmar
    >
    >
    P.S. Please don't go into a discussion about how the client should
    spend more money or hire someone full-time, etc. Budget constraints
    have dictated many of their decisions and will continue to do so. The
    programs have been sufficient to get by with and many of their reps
    are behind when it comes to technology and the latest hardware/
    software.
    >

    Comment

    • Michael C

      #3
      Re: Advice needed...

      "jmar" <jmarzion@yahoo .comwrote in message
      news:1179713949 .084335.286330@ b40g2000prd.goo glegroups.com.. .
      Any help would be appreciated. Of even greater interest is your
      opinions on the next topic. While trying to find out a bit about Vista
      compatibility, I came across an article which indicates the VB.net
      2003 and even VB.net 2005 may not be fully supported by Vista (http://
      https://www.theserverside.net/news/t...read_id=42426). This really
      surprised me and led to a discussion that I need your opinions on.
      This is only an issue for developing apps. You can run the compiled app on
      vista with no problems I believe. If you go with .net I would strongly
      suggest using C#. We moved from vb6 and initially to vb.net but then changed
      to C#. We were suprised how easy the change was and not one person in the
      company would consider moving back to vb.net.

      Michael


      Comment

      • Spam Catcher

        #4
        Re: Advice needed...

        "Michael C" <nospam@nospam. comwrote in
        news:exxoa62mHH A.4552@TK2MSFTN GP05.phx.gbl:
        This is only an issue for developing apps. You can run the compiled
        app on vista with no problems I believe. If you go with .net I would
        strongly suggest using C#. We moved from vb6 and initially to vb.net
        but then changed to C#. We were suprised how easy the change was and
        not one person in the company would consider moving back to vb.net.
        What's wrong with VB.NET?

        C# vs. VB.NET is really personal preference... underneath the covers it's
        the same framework and runtime.

        Comment

        • Spam Catcher

          #5
          Re: Advice needed...

          jmar <jmarzion@yahoo .comwrote in news:1179713949 .084335.286330
          @b40g2000prd.go oglegroups.com:
          3) After we get them at least functioning on Vista, we want to
          obviously upgrade them. What's the best route to go? We have to
          decide what programming environment to invest our time/energy in. The
          link above makes me question continuing on the VB.net journey (which I
          haven't even looked at in 4 months because of other projects). There
          has long been a thought of making them web-based to greatly simplify
          distribution/updgrades,etc. One of the potential negatives would be
          the requirement for internet access (often the reps are traveling
          pretty remotely) and/or speed of internet access. What helps you
          decide to go web-based vs stand-alone application? What positives/
          negatives should I be aware of?
          You could:

          1. Install Virtual PC/VMWare (I like VMWare more) and run an older OS to
          support your VB 4.0 app

          2. Rewrite the application using newer technology/language

          You can also consider using a "smart client". It's basically a web
          enabled desktop client with caching capabilities to allow the
          application to work when not connected to the Internet. When the client
          is reconnected, the data is synced up. However, building a smart client
          does require some knowledge of the .NET framework and data
          synchronization techniques - probably not something you can just pick up
          do without some experience.

          Depending on the complexity of your application a web application might
          not be a bad idea... however if you're not familiar with web application
          programming, there are some quirks which could be frustrating for a
          novice programmer.
          If we send them out as a stand-alone application, what language should
          we consider developing them in? Obviously we don't want to go down a
          road that ends up being a dead end in the near future.
          It doesn't really matter. VB.NET vs. C# is a religious war. Either
          languages are fine.

          Since you're a VB programmer, perhaps stick with a familiar syntax.

          Unlike previous Microsoft programming frameworks, .NET is supports
          multiple languages. All .NET languages share the underlying framework
          and thus share framework features. Also, binaries are interchangable - A
          C# DLL will work fine in a VB.NET project. In fact with VS.NET you can
          even mix and match languages in a solution :-)

          Comment

          • Michael C

            #6
            Re: Advice needed...

            "Spam Catcher" <spamhoneypot@r ogers.comwrote in message
            news:Xns9937195 28C2D7usenethon eypotrogers@127 .0.0.1...
            What's wrong with VB.NET?
            >
            C# vs. VB.NET is really personal preference... underneath the covers it's
            the same framework and runtime.
            It's pretty much the same but C# is aimed at the professional so has some
            features that vb.net doesn't. As an example C# supports pointers (beyound
            IntPtr). This might not be something you use every day but might need it one
            day and will be stuck if you're in VB.net. I'm sure there's other examples
            but I haven't used vb.net much.

            Michael


            Comment

            • Spam Catcher

              #7
              Re: Advice needed...

              "Michael C" <nospam@nospam. comwrote in
              news:Ox02no3mHH A.4188@TK2MSFTN GP02.phx.gbl:
              It's pretty much the same but C# is aimed at the professional so has
              some features that vb.net doesn't. As an example C# supports pointers
              (beyound IntPtr). This might not be something you use every day but
              might need it one day and will be stuck if you're in VB.net. I'm sure
              there's other examples but I haven't used vb.net much.
              I think you can do pointer arithmetic in VB.NET - but being a managed
              language it should be avoided under most circumstances. In fact C# only
              supports pointer functions if you declare your code as unsafe. If you
              google VB.NET vs. C# you'll find over 1.6 million articles debating the
              topic ... it's hardly a cut and dry issue - it's really a religious issue!

              Although VB.NET shares legacy syntax with classic VB, it's is unfair to say
              it is not "profession al" grade. Both languages share the underlying .NET
              framework and I yet to see a case where there is something that C# could do
              that is VB.NET could not do in one manner or another.

              Comment

              • Michael C

                #8
                Re: Advice needed...

                "Spam Catcher" <spamhoneypot@r ogers.comwrote in message
                news:Xns9937712 E3F5AAusenethon eypotrogers@127 .0.0.1...
                I think you can do pointer arithmetic in VB.NET
                It has a limited functionality that has *significantly* reduced performance.
                The main problem is you can't reference a pointer directly but have to copy
                memory to an array, modify it and copy back.
                - but being a managed
                language it should be avoided under most circumstances.
                It should also not be avoided when appropriate. Some functions currently
                need it. I use it for manipulating bitmaps.
                In fact C# only
                supports pointer functions if you declare your code as unsafe.
                That's true but the point is it's there if you need it. You could go all
                managed but easily double the time some functions would take. In C# you have
                the choice, in VB you don't.
                If you
                google VB.NET vs. C# you'll find over 1.6 million articles debating the
                topic ... it's hardly a cut and dry issue - it's really a religious issue!
                I think it is in that most professional developers are going to C#.
                Although VB.NET shares legacy syntax with classic VB, it's is unfair to
                say
                it is not "profession al" grade.
                I wouldn't say it's not "profession al grade" just that it is not as
                professional.
                Both languages share the underlying .NET
                framework and I yet to see a case where there is something that C# could
                do
                that is VB.NET could not do in one manner or another.
                You have seen something, pointers. There are other reasons also that i've
                read about but can't remember. Just things like having to declare option
                strict and redimming of arrays make it a bit less professional.

                Michael


                Comment

                Working...