I've noticed over the last several years that even when the control panel has been cleaned up and is running fast, the purchase process can crawl. I'm convinced that I'm loosing customers because of this.
I realize that this may be largely a problem with hsphere and there may not be anything...
Can anyone verify that the new compiler features also work? For example, can I use the new CSharp var keyword? Or does switching to 2.0 simply give us 3.5 API features?
No offense taken. I'm glad I'm not you. I charish my sleep too much :)
You can only do what you can do. Priorities have to be set. I'm cool with that.
Only "issue" I have is that the ticket system said 1 hour response time.
Anyone else having trouble. I've been getting this error since Friday when the upgrades started:
Error: Error processing credit card: For input string: ""
===========================
Trace log:
Error processing credit card: For input string: ""
at psoft.hsphere.Bill.charge(Bill.java:183)...
Heads up to any reseller using the support selector to direct to an external support system.
You apparently need to reset this as it came unglued during the upgrade.
First, I would be remiss if I did not congradulate Jodohost on how smoothly the upgrade to 3.0 has gone so far. I hardly noticed any down time on my sites. Amazing!
I have a few points of clarification I would like addressed now that I have access to the 3.0 control panel. All of these...
Yep. That's my understanding as well. Just being able to SAY we support ASP.NET 3.0 (even if no one actually uses it) would be a huge selling point. There ARE people searching for this and there ARE other hosting companies supporting it.
He's right. I have hosting accounts with two HSphere resellers. The other one moved to 2.5 recently and it took them a month to fully recover. The really amazing thing is, it was the 'nix side that had the most problems! And yes, the techs that did the upgrade spent time planning and still...
From experience.
I just moved from another company who did finally move to 2.5 so they could support ASP.NET 2.0 (because they couldn't or didn't figure out how to do it on 2.4 like JodoHost did.)
To say it broke things is an understatement. And guess where things broke the most? The...
It sounds like the ViewState hash is set to "auto" in the server's machine.config file. If this is true then you'd get a new key everytime the app pool recycles.
Fortunately, you should be able to override those values in web.config
Go here and create your machineKey element ASP.NET...