Advanced Forum Search Results
-
Without support for Mouswheel and right button etc people will just resort to browser specific hooks to use these functions. They are already doing it and we are now having to worry about writing cross browser supported silverlight code again because basic input functionality is missing from the SDK. Hopefully this is just a beta 1 issue, because ...
-
Hopefully this is just a bug in the beta 1, this is a pretty big deal if there is no binding to dependency properties and/or the datacontext is not automatically inherited from the parent containers.
-
That is pretty much exactly what I was doing. The only difference was the filename and content I was writing. It must be environmental if that works for you.
I'm running Windows Vista Ultimate and I have UAC enabled. Perhaps it's the UAC? I can try turning it off when I get home and see if it works.
The part that was failing for me ...
-
I am writing some simple settings.xml file fro saving some application state (not using ApplicationSettings) and I have the following issues:
I write out the settings int he Application_exit handler.
I then try to load them in the Application_startup handler.
The exit handler writes fine. The startup handler see's not files in the ...
-
It turned out to be caused indirectly by the following problem:
http://silverlight.net/forums/t/12103.aspx
Once I fixed the problem above this problem went away.
Thanks,
Bret
-
Mouse wheel support is more important than right click to me,however I believe the developer/designer of the application should be able to decide if they wants to use right mouse buttons, wheel support or even middle, 4th button support etc. I don't believe the framework developer (silverlight team) should be telling developers we have to ...
-
I'm using a HttpWebRequest in order to upload a large image file to the server (about 3-4megabytes).
I'm reading from the file stream and writing the file to the request stream in chunks and I'd like to report the percentage upload status to the user.
IE: 81921/3450000 bytes sent
However the code:int count;
byte[] buffer = new ...
-
Well I found a fix but not sure what I was doing wrong in the ticket creation above. Changing all of the above to the line:
FormsAuthentication.SetAuthCookie(userInfo.username, true, "/");
works now and the cookie is persistent and i no longer get errosr about it being invalid. Perhaps someone can explain what I was doing wrong ...
-
This has happened to me before too. Clear your entire browser cache and it should fix the problem.
-
I'm doing alot of testing with my application so decided to make the login cookie i create persistent so i don't have to keep logging in. I'm creating my cookies in asp.net using:
FormsAuthenticationTicket ticket = new FormsAuthenticationTicket(
1, // Ticket version
userInfo.username, // Username to be associated with this ...