<script runat=server></script> produces vars being undefined - why?

[isporter]

I plan to create an object in a javascript file, and then use that object and it's methods on both the server and the client side. Assume an ASP file with the code 'var product = new Product();'

The following declaration in the javascript file works fine:

function Product () {}
function Product.prototype.addToCart() {}

This declaration, however, produces a runtime error 'Object Expected' on the line creating the new product.

var Product = function() {}
Product.prototype.addToCart() {}

Simplifying the issue, I found that if I simply declared a string with 'var text = "hello world!";', and then called 'Response.Write(String(text));' in my asp page, it returns 'undefined'. However, if I remove the variable declaration from the javascript file, it returns a runtime error: 'text' is undefined.

Can anyone explain this behaviour and provide a solution?

 

[trollacious]

Client and server-side scripting don't interact like that. What's on the server is on one computer, and what happens on the client is a completely different computer disconnected from the server.

Lee

 

[isporter]

Lee, thanks for your response. I'm concerned I didn't make myself clear, so let me expand.

Assume a test.js file with

function Product () {}

in it.

You can include this script in an ASP page as follows:

<%@ language="javascript"%>
<script language="Javascript" src="test.js" runat="server"></script>

Then you can use

<% var myProduct = new Product() %>

in the ASP file to create a server-side instance of the Product object.

However, if in my .js file I use the notation

var Product = new function() {}

, it doesn't work. Why is this?