G
Guest
I am having a really hard time trying to get some client side code hooked up
in VS2005, ASP 2.0.
The code is in an .inc file (vbscript). The first problem I am encountering
is the ASP.NET page doesn't like vbscript and throws fits about the syntax.
Second, the page throws fits about the server side code tags (<% ...
%>),...are these supported anymore? Third, when I set the onclick event of a
client side HTML button it does not recognize the "public" method that I
specify (that is in the include file). I feel like there is some key piece of
information that I am missing that will make all of these issues fall into
place.
Essentially, what I need to do is access one or more local files on the
computer based on parameters that are sent to the server for processing. For
example, if a user clicks on a link I can pass a parameter to the server that
specifies the report the user is requesting, I can then return some
information about where to get the report (the file path...on another Report
Server), and then also where to put this report on the Users machine (client
code).
When I implemented this in ASP, I got it to work flawlessly and I was able
to do some string manipulation to get the client side code and the server
side code to work together nicely. I would like to get it updated to work
with our new ASP 2.0 webpages.
Any ideas on "re-inventing the wheel" in .NET?
Thanks,
- Mike
in VS2005, ASP 2.0.
The code is in an .inc file (vbscript). The first problem I am encountering
is the ASP.NET page doesn't like vbscript and throws fits about the syntax.
Second, the page throws fits about the server side code tags (<% ...
%>),...are these supported anymore? Third, when I set the onclick event of a
client side HTML button it does not recognize the "public" method that I
specify (that is in the include file). I feel like there is some key piece of
information that I am missing that will make all of these issues fall into
place.
Essentially, what I need to do is access one or more local files on the
computer based on parameters that are sent to the server for processing. For
example, if a user clicks on a link I can pass a parameter to the server that
specifies the report the user is requesting, I can then return some
information about where to get the report (the file path...on another Report
Server), and then also where to put this report on the Users machine (client
code).
When I implemented this in ASP, I got it to work flawlessly and I was able
to do some string manipulation to get the client side code and the server
side code to work together nicely. I would like to get it updated to work
with our new ASP 2.0 webpages.
Any ideas on "re-inventing the wheel" in .NET?
Thanks,
- Mike