I can't believe I'm installing Vista again...
-
It's not butter.[^] Come on, you knew that was coming.
Need custom software developed? I do C# development and consulting all over the United States. A man said to the universe: "Sir I exist!" "However," replied the universe, "The fact has not created in me A sense of obligation." --Stephen Crane
-
Really? I've been using VPC for some time since it's free and I never found a compelling reason to pay for VMWare. If you get the full Vista experience on it, then perhaps I've finally found my wallet.
Christopher Duncan Author of The Career Programmer and Unite the Tribes www.PracticalUSA.com
-
Seriously, does it? As per my knowledge no VMs yet support WDDM so Aero glass effect does not work anywhere.
-
Really? I've been using VPC for some time since it's free and I never found a compelling reason to pay for VMWare. If you get the full Vista experience on it, then perhaps I've finally found my wallet.
Christopher Duncan Author of The Career Programmer and Unite the Tribes www.PracticalUSA.com
I was going to use VPC, too, until I read what people were saying about it on the VMWare forums. I think MS did VMWare a real favor by putting out such a piece of junk. My Vista .vmdk files are less than 1GB. It's so nice to be able to install the latest IE in a VM without worrying about how badly your system is going to be hosed. I can get rid of the latest MS crapware faster than I can flush the toilet.
Best wishes, Hans
-
Are you sure? I thought it only worked under VMWare if the host OS was also Vista?
-
Normally, yeah. But Vista's Aero doesn't work in Virtual PC.
Christopher Duncan Author of The Career Programmer and Unite the Tribes www.PracticalUSA.com
Everyone knows VPC is for the birds! Even Bing knows this[^] :)
¡El diablo está en mis pantalones! ¡Mire, mire! SELECT * FROM User WHERE Clue > 0 0 rows returned Save an Orange - Use the VCF! Personal 3D projects Just Say No to Web 2 Point Oh
-
Normally, yeah. But Vista's Aero doesn't work in Virtual PC.
Christopher Duncan Author of The Career Programmer and Unite the Tribes www.PracticalUSA.com
Christopher Duncan wrote:
Vista's Aero
Ok I am confused now. What has Aero to do with your issue? All you need is to run the browser to test your site. Whether the browser window itself appears pretty or not should not have anything to do with the problem.
-
Normally, yeah. But Vista's Aero doesn't work in Virtual PC.
Christopher Duncan Author of The Career Programmer and Unite the Tribes www.PracticalUSA.com
Works fine in VirtualBox...
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001 -
I pushed a major overhaul of my business site night before last, and asked a few friends to bang on it to help flush out anything terribly embarrassing before I started a new promotion plan. I routinely test in IE7,8 and FF 3, then go back and do a sanity check on Safari and Chrome. All this happens in XP, as that's what all my machines are running. A friend emails me to say that a data entry form isn't working, i.e. he gets a validation prompt to enter text that his screen shot shows is clearly there. It's also clear from the shot that he's running Vista. Under the hood, the edit field is being compared to a session variable. Works in all the scenarios I test in but under Vista, for some reason, said session variable is blank. I switch it to a hidden text field, and everything works just fine. Conjure up the most offensive, politically incorrect, kid sister unfriendly phrases you can think of, and just imagine you heard me utter them with great enthusiasm. Bloody hell, session variables work everywhere else but not in Vista? I'm sure Rod Serling is sitting around the corner sipping cappuccino and having quite a chuckle at my current reality. This scenario seems completely unlikely and yet, that's the results I got. Session variables being a well used part of this system, I now have to install Vista and VS on a box so that I can test / debug other areas where I use them to see what the heck is going on. And so, I find myself fishing out those dusty old Vista installation disks and checking the cupboard to make sure I have an adequate supply of rum to ease the pain. I can handle html displaying differently in different browsers, but when server side stuff quits working depending on the OS... well, maybe I'll have that rum first.
Christopher Duncan Author of The Career Programmer and Unite the Tribes www.PracticalUSA.com
I have been doing ASP.Net for 8 years now. The session state has nothing to do with the Operating System. By Default Session objects are stored in memory in the ASPNet worker process. It has nothing to do with the client at all. Behind the scenes an identifier is used to determine the sessionId (and get the session information for the specific id browser) on each post back. This sessionId is usually stored as a cookie. If you set cookieless to true in the web.config the sessionId is stored in the query string and will disrupt the browsers ability to cache the page. So if during every postback the session information gets lost, one of two things is happening. The id is not being retrieved via the cookie. The browser may have cookies disabled. Or the apsnet worker process is recycled. This does occur normally and when you recycle the application pool.
I didn't get any requirements for the signature
-
I pushed a major overhaul of my business site night before last, and asked a few friends to bang on it to help flush out anything terribly embarrassing before I started a new promotion plan. I routinely test in IE7,8 and FF 3, then go back and do a sanity check on Safari and Chrome. All this happens in XP, as that's what all my machines are running. A friend emails me to say that a data entry form isn't working, i.e. he gets a validation prompt to enter text that his screen shot shows is clearly there. It's also clear from the shot that he's running Vista. Under the hood, the edit field is being compared to a session variable. Works in all the scenarios I test in but under Vista, for some reason, said session variable is blank. I switch it to a hidden text field, and everything works just fine. Conjure up the most offensive, politically incorrect, kid sister unfriendly phrases you can think of, and just imagine you heard me utter them with great enthusiasm. Bloody hell, session variables work everywhere else but not in Vista? I'm sure Rod Serling is sitting around the corner sipping cappuccino and having quite a chuckle at my current reality. This scenario seems completely unlikely and yet, that's the results I got. Session variables being a well used part of this system, I now have to install Vista and VS on a box so that I can test / debug other areas where I use them to see what the heck is going on. And so, I find myself fishing out those dusty old Vista installation disks and checking the cupboard to make sure I have an adequate supply of rum to ease the pain. I can handle html displaying differently in different browsers, but when server side stuff quits working depending on the OS... well, maybe I'll have that rum first.
Christopher Duncan Author of The Career Programmer and Unite the Tribes www.PracticalUSA.com
Christopher Duncan wrote:
well, maybe I'll have that rum first.
Windows Vista Rum Edition
- Easier installation! (just twist off the cap and pour)
- Better User Experience! (intense colors and visualizations)
- Be more productive! (You didn't know what you were doing anyway, so being passed out is a real productivity booster for those of us that don't have to fix the stuff you screwed up!)
- Improved Customer Satisfaction! (when you're hammered, you don't care that things are broke)
System Requirements: Users must be 21 years of age or older. Use only Windows Vista Rum Edition compatible shot glass.
:..::. Douglas H. Troy ::..
Bad Astronomy |VCF|wxWidgets|WTL -
I have been doing ASP.Net for 8 years now. The session state has nothing to do with the Operating System. By Default Session objects are stored in memory in the ASPNet worker process. It has nothing to do with the client at all. Behind the scenes an identifier is used to determine the sessionId (and get the session information for the specific id browser) on each post back. This sessionId is usually stored as a cookie. If you set cookieless to true in the web.config the sessionId is stored in the query string and will disrupt the browsers ability to cache the page. So if during every postback the session information gets lost, one of two things is happening. The id is not being retrieved via the cookie. The browser may have cookies disabled. Or the apsnet worker process is recycled. This does occur normally and when you recycle the application pool.
I didn't get any requirements for the signature
ToddHileHoffer wrote:
The id is not being retrieved via the cookie. The browser may have cookies disabled.
That had happened to me, IMHO that's the most common cause. You can try to run your site with the following config:
<sessionState cookieless="AutoDetect">
</sessionState>Jaime Febres The worst blog in the world
modified on Wednesday, June 3, 2009 12:47 PM
-
Christopher Duncan wrote:
well, maybe I'll have that rum first.
Windows Vista Rum Edition
- Easier installation! (just twist off the cap and pour)
- Better User Experience! (intense colors and visualizations)
- Be more productive! (You didn't know what you were doing anyway, so being passed out is a real productivity booster for those of us that don't have to fix the stuff you screwed up!)
- Improved Customer Satisfaction! (when you're hammered, you don't care that things are broke)
System Requirements: Users must be 21 years of age or older. Use only Windows Vista Rum Edition compatible shot glass.
:..::. Douglas H. Troy ::..
Bad Astronomy |VCF|wxWidgets|WTLDouglas Troy wrote:
Use only Windows Vista Rum Edition compatible shot glass.
Glass? Who uses a glass?
Christopher Duncan Author of The Career Programmer and Unite the Tribes www.PracticalUSA.com
-
Douglas Troy wrote:
Use only Windows Vista Rum Edition compatible shot glass.
Glass? Who uses a glass?
Christopher Duncan Author of The Career Programmer and Unite the Tribes www.PracticalUSA.com
Christopher Duncan wrote:
Glass? Who uses a glass?
Is that what they mean by "Open Source" ... no wonder so many people like it and think it's great. :rolleyes:
:..::. Douglas H. Troy ::..
Bad Astronomy |VCF|wxWidgets|WTL -
I have been doing ASP.Net for 8 years now. The session state has nothing to do with the Operating System. By Default Session objects are stored in memory in the ASPNet worker process. It has nothing to do with the client at all. Behind the scenes an identifier is used to determine the sessionId (and get the session information for the specific id browser) on each post back. This sessionId is usually stored as a cookie. If you set cookieless to true in the web.config the sessionId is stored in the query string and will disrupt the browsers ability to cache the page. So if during every postback the session information gets lost, one of two things is happening. The id is not being retrieved via the cookie. The browser may have cookies disabled. Or the apsnet worker process is recycled. This does occur normally and when you recycle the application pool.
I didn't get any requirements for the signature
As the morning has evolved, I've found that indeed it's not constrained to Vista, which at least gets Mr. Serling out of the loop because, like you, I couldn't imagine how the OS could be involved. The app is not being recycled, as I log that event. Had my Vista friend do more tests, which worked this time and this makes sense as I'm able to reproduce the problem myself now, but it's random in nature. Fire up the browser to a page, it works. Close the browser. Repeat 4 or 5 times. One or two will fail. But here's my personal favorite. Compose an email in Outlook with a link to the site, but don't send it. This requires you to use Ctrl+click to invoke the link. Fails 100% of the time if a browser isn't up, works 100% of the time if one is. Then send the email and bring it up from the Sent folder. No longer need the Ctrl, just a click. Works 100% of the time. So perhaps Mr. Serling is just on a lunch break. I'm using a shared hosting environment, and the thought occurs to me that using InProc makes me vulnerable to loss of session should server side memory management be taking place. Given the amount of sites on the server, I would think it most certainly does. Since I'm hoping to have a high traffic site one day :), I figure I'll move the session state management over to Sql Server. Slower, but less vulnerable in this regard. Now I know why the rum is always gone... :)
Christopher Duncan Author of The Career Programmer and Unite the Tribes www.PracticalUSA.com
-
Works fine in VirtualBox...
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001What's VirtualBox, and do you have it installed on Vista or XP?
Christopher Duncan Author of The Career Programmer and Unite the Tribes www.PracticalUSA.com
-
Christopher Duncan wrote:
Vista's Aero
Ok I am confused now. What has Aero to do with your issue? All you need is to run the browser to test your site. Whether the browser window itself appears pretty or not should not have anything to do with the problem.
Aero is a separate issue, and comes into the picture because I currently don't have a Vista environment to test in (even though this problem turns out to not a Vista thing). I'd rather have Vista environments in a VM for testing, especially since Weven is just around the corner, but without Aero it's not a complete testing environment for whatever I want to test.
Christopher Duncan Author of The Career Programmer and Unite the Tribes www.PracticalUSA.com
-
Aero is a separate issue, and comes into the picture because I currently don't have a Vista environment to test in (even though this problem turns out to not a Vista thing). I'd rather have Vista environments in a VM for testing, especially since Weven is just around the corner, but without Aero it's not a complete testing environment for whatever I want to test.
Christopher Duncan Author of The Career Programmer and Unite the Tribes www.PracticalUSA.com
Christopher Duncan wrote:
without Aero it's not a complete testing environment for whatever I want to test.
Sounds like a man who has written Flight control software.
-
Christopher Duncan wrote:
without Aero it's not a complete testing environment for whatever I want to test.
Sounds like a man who has written Flight control software.
Yeah. If I were you, I'd invest in Greyhound. :-D
Christopher Duncan Author of The Career Programmer and Unite the Tribes www.PracticalUSA.com
-
Normally, yeah. But Vista's Aero doesn't work in Virtual PC.
Christopher Duncan Author of The Career Programmer and Unite the Tribes www.PracticalUSA.com
Christopher Duncan wrote:
Normally, yeah. But Vista's Aero doesn't work in Virtual PC.
It doesn't?
The world is a stage and most of us are desperately unrehearsed. —Sean O’Casey, Playwright
-
It's not butter.[^] Come on, you knew that was coming.
Need custom software developed? I do C# development and consulting all over the United States. A man said to the universe: "Sir I exist!" "However," replied the universe, "The fact has not created in me A sense of obligation." --Stephen Crane