Showing posts with label weird. Show all posts
Showing posts with label weird. Show all posts

Monday, March 26, 2012

Trouble editing HTML Elements version 0.6

Hi
I just encountered something very weird. I opened an existing aspx fileto make some changes. When I click on an HTML element, such as a textbox, I get the open squares that say it is selected. The Propertieswindow opens up on the right but when I try to make any changes in thatwindow, the open squares become gray squares around the HTML element.Certain properties (e.g. Type) can be changed. Others such as ID cannot be changed. However I can go into the HTML code and make thechanges there. I am using version 0.6 of ASP.NET.
Any ideas on what happened? If it helps, I am working on the Guest Book example in Chapter 10 of Mike Pope's starter book.
Danny Low

version 0.6 of ASP.NET


As far as I know there has never been a ver. 0.6 of Asp.Net. You are either using ver. 1.0, 1.1 or 2.0. Are you perhaps talking about some kind of development tool here, like Visual Studio?

As far as I know there has never been a ver. 0.6 of Asp.Net.
When you ask for version number with Help->About the window thatpops up says version 0.6 build(812). This is what I downloaded from theasp.net download section.
Danny Low

What window is this? Asp.Net is part of the .NET Framework and does not come with an Interface. There are three versions of .NET; 1.0, 1.1 and 2.0. Is it Web Matrix your are referring to??
Yes, it is Web Matrix that I am referring to. All I did was save myaspx file at a convenient stop point and shut down my system for thenight. The next day when I resumed working on the sample program, I noticed the weird behavior of not being able to edit some propertiesof the page elements when in the Design mode. And it is not just theexisting elements but any new elements that I add to the page.
Danny

Tuesday, March 13, 2012

trouble with viewstate

Hello,
I had a really weird problem that occured on one of our site. (occur 2 times
in 3 years)
The client 1 have fill the form1 and submit it, for some reason the page was
postback to the client 1 but the informations that was on the form after the
postback was not the informations of the client 1 but the informations of
another client (on another computer) that had filled this form 5 minutes
before.
we never save this information in any variables, enableviewstate have been
set to true to save the data on postback
here are some other informations:
Asp.net version 1.1
code vb.net
Framework 1.1, no servcie pack install
server = Windows 2000 sp4
the page is ssl (https)
EnableViewStateMac is set to true on the web.configi'd suggest looking elsewhere for the cause. Probably the server is pulling
the wrong data based on id. It's unlikely for that type of thing to happen
due to viewstate confusion based on the way viewstate works.
Regards,
Alvin Bruney [MVP ASP.NET]
[Shameless Author plug]
The Microsoft Office Web Components Black Book with .NET
Now Available @. www.lulu.com/owc
Forth-coming VSTO.NET - Wrox/Wiley 2006
----
"sdrouins" <sdrouins@.discussions.microsoft.com> wrote in message
news:1BCC0DE6-680E-4558-A60A-8C80332BB976@.microsoft.com...
> Hello,
> I had a really weird problem that occured on one of our site. (occur 2
times
> in 3 years)
> The client 1 have fill the form1 and submit it, for some reason the page
was
> postback to the client 1 but the informations that was on the form after
the
> postback was not the informations of the client 1 but the informations of
> another client (on another computer) that had filled this form 5 minutes
> before.
> we never save this information in any variables, enableviewstate have been
> set to true to save the data on postback
> here are some other informations:
> Asp.net version 1.1
> code vb.net
> Framework 1.1, no servcie pack install
> server = Windows 2000 sp4
> the page is ssl (https)
> EnableViewStateMac is set to true on the web.config
>
>
You're right Alvin..
The prbleme was in the outputcaching... not a probleme with viewstate
Thanks
"Alvin Bruney - ASP.NET MVP" a écrit :

> i'd suggest looking elsewhere for the cause. Probably the server is pullin
g
> the wrong data based on id. It's unlikely for that type of thing to happen
> due to viewstate confusion based on the way viewstate works.
> --
> Regards,
> Alvin Bruney [MVP ASP.NET]
> [Shameless Author plug]
> The Microsoft Office Web Components Black Book with .NET
> Now Available @. www.lulu.com/owc
> Forth-coming VSTO.NET - Wrox/Wiley 2006
> ----
>
> "sdrouins" <sdrouins@.discussions.microsoft.com> wrote in message
> news:1BCC0DE6-680E-4558-A60A-8C80332BB976@.microsoft.com...
> times
> was
> the
>
>

trouble with viewstate

Hello,
I had a really weird problem that occured on one of our site. (occur 2 times
in 3 years)

The client 1 have fill the form1 and submit it, for some reason the page was
postback to the client 1 but the informations that was on the form after the
postback was not the informations of the client 1 but the informations of
another client (on another computer) that had filled this form 5 minutes
before.

we never save this information in any variables, enableviewstate have been
set to true to save the data on postback

here are some other informations:
Asp.net version 1.1
code vb.net
Framework 1.1, no servcie pack install
server = windows 2000 sp4
the page is ssl (https)
EnableViewStateMac is set to true on the web.configi'd suggest looking elsewhere for the cause. Probably the server is pulling
the wrong data based on id. It's unlikely for that type of thing to happen
due to viewstate confusion based on the way viewstate works.

--
Regards,
Alvin Bruney [MVP ASP.NET]

[Shameless Author plug]
The Microsoft Office Web Components Black Book with .NET
Now Available @. www.lulu.com/owc
Forth-coming VSTO.NET - Wrox/Wiley 2006
-----------------

"sdrouins" <sdrouins@.discussions.microsoft.com> wrote in message
news:1BCC0DE6-680E-4558-A60A-8C80332BB976@.microsoft.com...
> Hello,
> I had a really weird problem that occured on one of our site. (occur 2
times
> in 3 years)
> The client 1 have fill the form1 and submit it, for some reason the page
was
> postback to the client 1 but the informations that was on the form after
the
> postback was not the informations of the client 1 but the informations of
> another client (on another computer) that had filled this form 5 minutes
> before.
> we never save this information in any variables, enableviewstate have been
> set to true to save the data on postback
> here are some other informations:
> Asp.net version 1.1
> code vb.net
> Framework 1.1, no servcie pack install
> server = windows 2000 sp4
> the page is ssl (https)
> EnableViewStateMac is set to true on the web.config
>
You're right Alvin..
The prbleme was in the outputcaching... not a probleme with viewstate

Thanks

"Alvin Bruney - ASP.NET MVP" a écrit :

> i'd suggest looking elsewhere for the cause. Probably the server is pulling
> the wrong data based on id. It's unlikely for that type of thing to happen
> due to viewstate confusion based on the way viewstate works.
> --
> Regards,
> Alvin Bruney [MVP ASP.NET]
> [Shameless Author plug]
> The Microsoft Office Web Components Black Book with .NET
> Now Available @. www.lulu.com/owc
> Forth-coming VSTO.NET - Wrox/Wiley 2006
> -----------------
>
> "sdrouins" <sdrouins@.discussions.microsoft.com> wrote in message
> news:1BCC0DE6-680E-4558-A60A-8C80332BB976@.microsoft.com...
> > Hello,
> > I had a really weird problem that occured on one of our site. (occur 2
> times
> > in 3 years)
> > The client 1 have fill the form1 and submit it, for some reason the page
> was
> > postback to the client 1 but the informations that was on the form after
> the
> > postback was not the informations of the client 1 but the informations of
> > another client (on another computer) that had filled this form 5 minutes
> > before.
> > we never save this information in any variables, enableviewstate have been
> > set to true to save the data on postback
> > here are some other informations:
> > Asp.net version 1.1
> > code vb.net
> > Framework 1.1, no servcie pack install
> > server = windows 2000 sp4
> > the page is ssl (https)
> > EnableViewStateMac is set to true on the web.config
>