This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
Hey Guys, I'm using the MVC CTP 2 and I'm getting the following exception: Event handlers can only be bound to HttpApplication events during IHttpModule initialization.I seem to get this with any interaction with Lightspeed inside an action... specifically Entity.IsValid & Entity.FindOne<> Thoughts? Also, while I'm asking a question, can you give me an example of how to use the RangeValidationRule<>? Ps. I'm using one of the nightly builds. The LightSpeed.dll version is 1.2.214.7203. |
|
|
|
|
Hi Charles, I have tried recreating this issue but cannot do so (latest nightly build, FindOne call in an action in a controller). Everything seemed to work fine. Is it possible for you to provide a repro of your issue for me to test further? We provided the ValidationRule for range however it wasn't accessible as an attribute. I've just added an attribute to enable this and it will be included in the nightly build tonight (note: you could still use the rule manually in the OnValidate method). What sort of range testing do you want to achieve? Just integer testing or more complex testing? Thanks, John-Daniel Trask |
|
|
|
|
Hi JD, Thanks for the reply. I'll grab the latest nightly and have another look at it tonight @ home. If I can still reproduce it I'll post some code for you to test. I did notice that it only occured running it in IIS and not visual studio's built in web server. I actually just wanted to test the length of string and thought that that ValidationRule may do the trick. I have since created 3 custom validation attributes (min, max and range) that do this for me. Cheers, |
|
|
|
|
Yeah, I’m still getting the exception with the latest build unfortunately. To recreate, follow these steps:
That's all I had to do... please tell you you get the same! :-) |
|
|
|
|
Hi Charles, Thanks for your details on creating the repro. We have no created this scenario here and are working on resolving the issue. The problem relates to using the integrated ASP.Net pipeline in IIS7 (which doesn't exist in the VS integrated webserver). I hope to have a fix to this issue in the next few days. Thanks for providing your feedback, John-Daniel Trask |
|
|
|
|
This was fixed in last nights nightly build. |
|
|
|
