You searched for the word(s): userid:684892

More Search Options

RSS Available

• Re: Code that runs once per any request

  Ha, my eyes fails me once again! I really need to get new glasses... I was facing a similar problem and found some quirks along the line. Thought I'd share them and now you know! But you're right. I'm talking about once per app stuff, not once per request. I would however refrain from putting code in the Global.asax file. It's works sure, but a module is just as simple to write and it keeps the code out of that file. It's a little more orginized be it time consuming process. But

  Posted to ASP.NET MVC (Forum) by leidegre on 7/26/2008

• Re: Stateful ASP.NET MVC?

  I'm not clear on the LINQ to SQL. Is this a dependency? LINQ to SQL is primarily my data model to the project which this is being developer for. I'm new to LINQ to SQL and thought I'd try it out. What it is, is just a way of handling form data. And I use type information to limit the amount of properties I build into the parser collection. It was an optimization necessary to prevent a cyclic-reference scenario which could occur if Type A had a property of Type B and type B had a property

  Posted to ASP.NET MVC (Forum) by leidegre on 7/26/2008

• Re: Code that runs once per any request

  There's generally only one way to go about this and it's not just an IHttpModule which some of you might think. More than one instance can be created for any HttpModule by the runtime. So even if you used a HttpModule you should consider the following... A fairly all around solution for code that needs to run exactly once is type initialization code. Basically a static constructor. It's always legal to write: 1 public class SomeType 2 { 3 static SomeType() 4 { 5 //... 6 } 7 } ...and code

  Posted to ASP.NET MVC (Forum) by leidegre on 7/21/2008

• Re: URL rewriting and rendering results

  I've built a small test suit for this and I've made it work but there's a couple of problems. Everybody seem to hate cookies. But they do the job, so I've narrowed it down to relying on the Path and Max-Age=30 properties to ensure that the cookie is almost unique for the request. If the same user requested the same URL concurrently there's definitely something undefined about my approach. That's not to say that it does not have a solution. Moving on, upon receiving a request

  Posted to HttpHandlers and HttpModules (Forum) by leidegre on 7/21/2008

• Re: Stateful ASP.NET MVC?

  The thread started out as some random question about stateful web applications but it's kind of ventured beyond that. Anyhow, do you know how this TempData persisted, do you know how MVC tracks the TempData dictionary between requests? John

  Posted to ASP.NET MVC (Forum) by leidegre on 7/21/2008

• Re: URL rewriting and rendering results

  That won't do squat. This is not so much making URL rewriting work as it has to do what you get with the browser. I think this will have more to do with the client browser behaviour than anything else. One thing you might wanna prevent is refreshing a successful post. If I post data and it's successfully handled, well then I don't want F5 to me about resubmitting that form data. It should only refresh the response view. Is there no better way than to relocate with the location HTTP header

  Posted to HttpHandlers and HttpModules (Forum) by leidegre on 7/20/2008

• Re: Stateful ASP.NET MVC?

  I'm not sure what you're talking about, could you explain a bit more what your approach exactly accomplish, it sounds interesting. It might be good to point out that this is not ASP.NET MVC. It's work derived from the general design of ASP.NET MVC. You can not just run your ASP.NET MVC application in this framework I've built. It's greatly different in how it handles things. Also, there is no such thing as a ViewState in this framework.

  Posted to ASP.NET MVC (Forum) by leidegre on 7/20/2008

• Re: Stateful ASP.NET MVC?

  superevanc, I promised to get back to you and I'm about to do so. A month or so has passed and there's a lot of things to talk about, but there's little of the actual code that I can share. The company I'm working for maintains ownership of the product so I can not simply provide that. But my ideas are my own and I like to share them. So what I've built is sort of like ASP.NET MVC++ and it has nothing to do with C++ it's just that I've derived a lot of the architectural

  Posted to ASP.NET MVC (Forum) by leidegre on 7/19/2008

• URL rewriting and re-seating rendering results (updating the HTTP Location:)

  There seem to be a mismatch between a rewritten URL and what resulting view is rendered. View is here just a word for what shows up the browser. The problem is simply confusing for the end-user. Imagine I type the URL and I end up with a specific view and now change the URL a bit and start hitting the back and forward buttons. At some point you run into a case where the URL no longer matches the expected view. That's a bad thing. What I would like to be able to do is to tell the browser that

  Posted to HttpHandlers and HttpModules (Forum) by leidegre on 7/19/2008

• Re: What's up with routes and the ControllerFactory?

  Here's something which relates to my topic of no strings! The ASP.NET compilation services can actually be used to pseudo-type check this information. The runtime will create assemblies with all your Page instances that handle requests. Those are currently defined by a string, which upon renaming will stop working. During the compilation process the ASP.NET runtime will provide these strings for you, as they should be entered or used by the BuildManager (currently used by ASP.NET MVC Framework

  Posted to ASP.NET MVC (Forum) by leidegre on 6/19/2008