WebDude & anyone else still using Tango 2000…
I’ve updated the page on the Witango.com site (Products > What’s New) so that it has working links to the two “What’s New” documents. The top part of the page talks about migration from Tango 2000 to Witango 5. The bottom part is about moving from 5.0 to 5.5. I strongly recommend that you read both documents carefully, as there are a few major differences, as we’ve pointed out, and they are explained in detail here. Let me know if you have any problems with the PDFs. As for advice regarding upgrading, I’m of two minds here. On the one hand, the file format in version 6 will be compatible with 5.5, therefore you can begin working on your migration now (moving to 5.5) knowing that you won’t be wasting your time. However, moving to the 5.5 platform may have its own issues, especially for OS X users, JDBC users, and those wishing to use the newest hardware and software. In other words, I do recommend using 5.5 as a tool in your migration, but you may want to wait until 6 is out before upgrading your production environment. The one caveat to this rule is that if you are using older hardware and software (or can do so with virtualization) then v5.5 can still be quite effective. Any v5.5 licenses which are purchased from now on will automatically get a free upgrade to v6. So if you are committed to moving to v6 when it comes out, then there is no risk in getting an early start on that process. Robert Witango From: WebDude [mailto:[email protected]] Sent: Tuesday, August 10, 2010 3:28 PM To: [email protected] Subject: Witango-Talk: Windows 7 Server Folks... I am so excited about the latest developments, I almost peed myself. I have been holding out for years on upgrading... pretty much because I spent so much on the Corporate Server. But, since there seems to be new life being pumped into the product, I am seriuosly considering buying, at the minimum, 2 professional servers. The reason for this post is I have some concerns. I am still using Witango 2000 and very happy with it. I have it installed on 3 servers and never really had any issues. 2 of the servers are Win2k and one is a 2003. We run about 70 websites, some getting about a half million visits per month. I also have some very important corporate clients that are very critical when it comes to uptime, speed, etc. (yeah, I know... but corporate america can be kind of dumb when it comes to this stuff... still running such an old version). Nothing is clustered, all servers are dedicated to specific sites. All tie into a single database server. Anyway, I am going to be purchasing a few Windows Servers and would like to load the new platform on them. I know there are some adjustments that will need to be made. I believe that one of these is setting the default scope of all unscoped variables to user... is that correct? What I need to know is any other caveats that some of you may have run into. (i.e. do I actually have to open and save each taf before they will work with a new server?) I am thinking of porting 1 site at a time. I will have the luxury of having new servers configured and ready to go along with the old servers. Any help would be greatly appreciated. I just landed some pretty hefty contracts and would like to keep using Witango as it is my program of choice for almost all of our development. I also would like to try to get Witango into the mainsteam a bit more, too. Not sure how to do this, but I would think if we could put our collective heads together, we might be able to come up with something. I do work for some very big corporations and, though I don't want to drop any names here, I might be able to get them to support the product a bit. Not sure how to approach them, just thinking out loud. Endoresements maybe? I am not sure how this stuff works. Thanks! _____ To unsubscribe from this list, please send an email to [email protected] with "unsubscribe witango-talk" in the body. ---------------------------------------- To unsubscribe from this list, please send an email to [email protected] with "unsubscribe witango-talk" in the body.
