Versioning in CE

Last post 07-18-2007, 10:29 AM by afroblanco. 6 replies.
Sort Posts: Previous Next
  •  07-15-2007, 11:43 PM 31565

    Versioning in CE

    Can you please use versioning in CE so that we can read the version in .NET code and advise our users if they are not using the latest version. It's very difficult for us to ensure our users have the correct version.
     
    Further, can you please show a list of fixes in each release.
     
    When you say issues are fixed, what:

    1. Is the new DLL's Version #. You need to be incrementing the versioning so we know which is the latest DLL.

    Do not leave the DLL as 6.0.0.0.

    2. What other files are affected? There are hundreds of files in the release version and we can't keep re-releasing all of them. We have an incremental distribution system hat allows us to add the files that have changed.

    Please specify which files have  changed.

  •  07-16-2007, 12:38 PM 31578 in reply to 31565

    Re: Versioning in CE

    fredd,
     
    Version 6.1 will be released in August.
     
    However we will never stop improving the version 6.0 and fix bugs based on the client feedbacks.  If anything is urgent to our clients, it will be urgent issue to us.
     
    We will fix it as soon as possible and put the update software in the download section. The update log will be post at:
     
     
    If you are not comfortable with the approach, please wait for the version 6.1.
     
     
     
     
     

    asp.net Chat http://cutesoft.net/ASP.NET+Chat/default.aspx
    Web Messenger: http://cutesoft.net/Web-Messenger/default.aspx
    asp.net wysiwyg editor: http://cutesoft.net/ASP.NET+WYSIWYG+Editor/default.aspx
    asp wysiwyg html editor: http://cutesoft.net/ASP
    asp.net Image Gallery: http://cutesoft.net/ASP.NET+Image+Gallery/default.aspx
    Live Support: http://cutesoft.net/live-support/default.aspx

  •  07-16-2007, 4:07 PM 31586 in reply to 31578

    Re: Versioning in CE

    Adam,
     
    You are missing the point.
     
    Versioning has sub-version numbers, and you should be using those.
     
    Eg. 6.0.2524.1375
     
    and
     
    6.0.3214.4892
     
    or simply:
     
    6.0.0.135
    6.0.0.136
     
    It's all still V6.0, but the sub-versions identify the currency of release.
     
    this is pretty standard. Can you please start doing that?
  •  07-17-2007, 4:34 AM 31604 in reply to 31586

    Re: Versioning in CE

     
    If the control version number is changed, developers will have to recompile the whole project. No matter how small.
     
     
     
     

    asp.net Chat http://cutesoft.net/ASP.NET+Chat/default.aspx
    Web Messenger: http://cutesoft.net/Web-Messenger/default.aspx
    asp.net wysiwyg editor: http://cutesoft.net/ASP.NET+WYSIWYG+Editor/default.aspx
    asp wysiwyg html editor: http://cutesoft.net/ASP
    asp.net Image Gallery: http://cutesoft.net/ASP.NET+Image+Gallery/default.aspx
    Live Support: http://cutesoft.net/live-support/default.aspx

  •  07-18-2007, 2:25 AM 31649 in reply to 31604

    Re: Versioning in CE

    In .net 1.1 they will probably have to to do that yes, but I don't think it will be a problem in ASP.NET 2.0. Anyway I would gladly recompile if we could get versioning. It is always a problem to figure out what version a customer has when they have a problem with the editor.
    Maybe the version number also could be printed in top of the help page.

  •  07-18-2007, 10:22 AM 31660 in reply to 31604

    Re: Versioning in CE

    Adam,
     
    That's BS. The whole idea of versioning is to ensure consistency. You are breaking all the standard rules and causing us real trouble distributing updates. If a developer CHOOSES TO INSTALL A NEW VERSION OF CE, then they are fully prepared to recompile if necessary. That's the way it is with other components and it should be the same with CE
     
    You should not be making choices for us. It's totally confusing.
  •  07-18-2007, 10:29 AM 31661 in reply to 31565

    Re: Versioning in CE

    HAH!  It's good to see that I'm not the only one who has a problem with the lack of versioning in CE 6.0.  I'll be honest, this whole thing has really tested my patience.  Here's a thread that I opened on the subject.

    This is my theory - 6.0 was supposed to be bug-free.  However, it was buggy as all hell, which is why Adam has to make updates to it, like, every 3-4 days.  Even if he was using versioning, this would still be a pain in the ass.  Unless your software is in beta, you should NOT have to do this many updates.  I should not have to check a stupid website every day to see if a new version is up.  A rich text editor is really but a small component of my software, and I shouldn't have to spend this much time and effort on it.  I'm sorry Adam, but your software just isn't THAT important.

    Anyway, the lack of versioning makes everything even worse.  I can't possibly stress how unprofessional this is.  I think it would be hilarious if a real software company were to eschew version numbers, and instead say, "Umm, we're not using version numbers.  Instead, we're going to update our software every few days without telling you.  It will be your job to check our downloads page to see if a new version is up.  Oh yeah, and since we won't be using version numbers, you'll have to check the date when the file was posted.  Likewise, you will have no way of referring to your version number when asking for customer support, and there will be no easy way for you to tell which version you are running.  Finally, we won't give you any indication of when you can expect an actual bug-free release of our code.  You just need to keep checking our downloads page every day for the rest of your life.  Have fun!"

    And when I've asked when we can expect an actual bug-free version of the code - you know, an actual release that will be good for a while - I get this lame line about how, "We're never going to stop improving our product."  Like I'm asking them to make a final version of their software and then never add any new features again.  This is forehead-slappingly stupid.  I seriously wanted to pound my head on the desk when I read this.  Listen, I'm not asking for a "FINAL VERSION."  I'm asking for an ACTUAL RELEASE.  One that won't be updated again until a few months have passed.  You know, like what every other company on this planet does?

    Here's a hint for the Cutesoft people - next time you want to release a buggy, experimental version of your code, put it in beta and save us the trouble, OK?  And while you're at it, take a look at how other software companies operate.  THEY USE VERSION NUMBERS!
View as RSS news feed in XML