Spring.Web App Deployment Problem...Maybe

[spmva]

I'm not sure if this is a Spring problem or not, but I've never had this issue prior to having Spring in the mix, so I thought that I should start here for troubleshooting. Plus...the fact that I always seem to get such great help here doesn't hurt either. {smile}

I'm deploying my wonderfully made Spring.Web app from my local machine to a development/testing server. I've always used the simple method of doing this operation, by utilizing the "Copy Project" function in Visual Studio. As usual "Copy Project' went through this time without a hitch.

When I attempt to test the newly deployed application, the login screen accepts my username/password and loads the application home page. When I click on any LinkButton, however, I get an error that appears to be in the browser (doesn't get to the server) and the little "Error on page." icon sits at the bottom right corner. Clicking on that yields little information, except that the error occured at line: 1 char: 1 and that the error was "Object expected".

Would it be a good guess to assume that this issue has something to do with the generated javascript on the page for handling postback? I don't know much javascript, but for some reason this particular line looks suspicious:
theform = document.masterPage:Form1;
that colon just doesn't look right to me. I've looked at some of my other ASP.Net pages generated on my local machine and none look like that.

Any thoughts would be appreciated.

Best regards,

Steve

[Aleks Seovic]

This is a well-known issue with ASP.NET 1.1 without SP1 applied -- it generates a wrong name for the form element, which breaks the postback script. This has been resolved in SP1 for the .NET Framework, so you will have to apply it to your test server.

Same thing would happen on your local machine if you didn't have SP1 installed.

I should probably start Spring.Web FAQ and put this issue there -- it has come up on numerous occasions already.

Later,

Aleks

[spmva]

Thanks. I'll give it a shot. The solution is not surprising...this particular server has been collecting dust for some time now. Interesting that I'd never heard of that issue before.

Didn't mean to throw too much blame Spring's way :oops: . I should have known it was those Microsoft guys {smile}.

[Aleks Seovic]

Yeah, you should always assume it's Microsoft's fault first ;)

It wouldn't be an issue if you didn't use master page. It pops out because master page is a naming container that is basically a nested control in the page and your form is defined within it. Failure boils down to form's UniqueID being used instead of ClientID within the script.

The issue came up several times before, related to master page postbacks being swallowed, script errors within SpringAir sample app, etc. Rick recently had another unrelated problem that was also non-issue on SP1 machine, can't remember exactly what it was.

Anyway, we will make sure that release notes state that Spring.Web requires ASP.NET 1.1 SP1 or higher and place a warning in a prominent place within a docs stating the same.

Later,

Aleks