views:

246

answers:

1

I have a jQuery function in a .js file, and the function requires a querystring parameter to be passed.

If I try to use the CompositeScript feature in the ScriptManager, it pukes on the file that has the querystring. Is there any way around this?

A: 

I was trying to do the same thing and the error I got was something like "URL was not a virtual path" so I'm assuming the path must be virtual. So you may not be able to do this as appending the querystring variable to the path will cause the URI to choke.

You could set your variable in the page or masterpage if global, thus you wouldn't need to pass a querystring.

Might be a way to do what you are accomplishing, but my guess would be that you would have to add in another step, like a route to the jsfile.js?qv=whatever to jsfile.js, or add in an httphandler. Probably more trouble than it is worth.

Just guesses.

infocyde
Or just ditch the compositescript and have the link to the script outside of the scriptmanager.
infocyde
I have it working using ScriptManager1.Scripts.Add() This is not my "problem" I want to be able to use the CompositeScript simply because it combines the JS. Now that I think about it... that's probably why since the CompositeScript builds a querystring of it's own.
rockinthesixstring