> This is the default behavior for .NET applications. The .NET runtime > will convert IL code to machine code, the ASP.NET runtime will compile > classes in App_Code and code begind files. This will be done on > request, so initial invokes are much slower than when running the > second call.
Yeah, I'm cool on that, I'm pedanctic enough to precompile off the command line, what I'm saying is that the first time I make a call to a function on a page, it runs slower than a subsequent call. Browse away and return to the page, without refreshing any DLLs, and there is still an initial performance hit. Frankly I'm inclined to think I've done something braindead somewhere but I've no idea what it could be, I'll see how the custom serializer affects things. So I can rule things out, when do the trace messages get fired? Does the End Reflection mean the entire invoke is complete, or just that the initial period of searching for the method is done? I'd look it up in reflector, but I'm lazy... --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ajax.NET Professional" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/ajaxpro The latest downloads of Ajax.NET Professional can be found at http://www.ajaxpro.info -~----------~----~----~----~------~----~------~--~---
