Editing ASPX.VB File

  • Thread starter Thread starter JeremyWoertink
  • Start date Start date
J

JeremyWoertink

I have an app that I need to make changes to, and on my local copy I
have a start.aspx.vb file that I edited and tested, now when I go to
the app on the server, it doesn't show any of the .vb files, only
the .aspx files. How can I make it show me the .vb file?



~Jeremy
 
It looks like your application uses the "inline" method of coding. Look in
your .aspx files for sections that are blocked off like this:

<script runat="server" ...>


</script>

Your code is most likely in one or more of these.
 
It looks like your application uses the "inline" method of coding. Look in
your .aspx files for sections that are blocked off like this:

<script runat="server" ...>

</script>

Your code is most likely in one or more of these.
Click to expand...

no, that's not what i'm looking for. I don't want to put VB code into
my HTML files. I think that's horrible that ASP even allows for that.
I want to put it into the .VB where it belongs. The server that the
application is running on doesn't have visual studio, so I have to
open all these files with notepad. The file I want to open is a hidden
file. I have "show all hidden system files and folders" and all that
stuff, so I can see the desktop.ini and everything cool like that, so
it must be a special ASP.NET hidden file. I have 2 copies of the
application. One on my local machine and one on my server. They do the
exact same thing, but as far as what I see in the folders, I see 2
different things. My local copy shows me all the aspx.vb files, and
the one on the server doesn't I want to know how I can show these
files.



~Jeremy
 
no, that's not what i'm looking for. I don't want to put VB code into
my HTML files. I think that's horrible that ASP even allows for that.
I want to put it into the .VB where it belongs. The server that the
application is running on doesn't have visual studio, so I have to
open all these files with notepad. The file I want to open is a hidden
file. I have "show all hidden system files and folders" and all that
stuff, so I can see the desktop.ini and everything cool like that, so
it must be a special ASP.NET hidden file. I have 2 copies of the
application. One on my local machine and one on my server. They do the
exact same thing, but as far as what I see in the folders, I see 2
different things. My local copy shows me all the aspx.vb files, and
the one on the server doesn't I want to know how I can show these
files.

~Jeremy- Hide quoted text -

- Show quoted text -
Click to expand...

Hi Jeremy

..vb files are not hidden nor do they have any special attributes to
hide them from view. If (as Patrice has suggested) the site has been
compiled then you'll find the DLL files in a "bin" directory. If you
have used the "Publish web site" tool in VS then it will have been
compiled. You don't have to do this if you prefer not to. Use "Copy
web site" instead. In fact the latter method of deployment makes
maintenance and upgrades much easier because it keeps track of changed
files whereas "Publish" deletes everything and replaces the site
wholesale. This mode of deployment is not essential unless it is a
large site where visitors typically access a wide variety of different
pages. Otherwise server caching will compensate for the time it takes
to parse source code and there will be no particular performance
problems with a non-compiled web site.

HTH

Phil Hall
 
I wasn't suggesting that you *should* use the inline model, I was saying
that if you can't find source code files anywhere (I didn't realize you did
have them on your local copy), then this might be how the pages were
created.

You won't find the .vb files on the server because you wouldn't typically
want your source code available to the server. You do your development on
your local copy and then deploy the .aspx files (client code) along with the
project assembly (.dll) to the server.

As a rule of thumb, you never want to develop on the production
files/server.
 
I wasn't suggesting that you *should* use the inline model, I was saying
that if you can't find source code files anywhere (I didn't realize you did
have them on your local copy), then this might be how the pages were
created.

You won't find the .vb files on the server because you wouldn't typically
want your source code available to the server. You do your development on
your local copy and then deploy the .aspx files (client code) along with the
project assembly (.dll) to the server.

As a rule of thumb, you never want to develop on the production
files/server.
Click to expand...

Sweet. Thanks everyone for the help. It never really answered my
question, but it does give me a better way to do this. I am used to
doing web applications in rails, so this whole ASP stuff is new to me.
I think I might have figured out what it was. The version on the
server was VS 7.1 and the one on my machine is VS 8, so when I copied
the one from the server to my computer and opened it, it wanted to do
a conversion wizard. After it was done, I had like 9 new folders and
all kinds of new files including the aspx.vb files that weren't there
before. So what I did was I just updated the app, then copied it back
onto the server. The app is for intranet use, so no one sees it on the
internet anyway. Thanks again.


~Jeremy
 
It never really answered my
question
Click to expand...

Maybe the problem is that you didn't explain what the server is for.
If it is a webserver, it doesn't need to have *.vb files to make your
site working.

The version on the
server was VS 7.1 and the one on my machine is VS 8, so when I copied
the one from the server to my computer and opened it, it wanted to do
a conversion wizard. After it was done, I had like 9 new folders and
all kinds of new files including the aspx.vb files that weren't there
before. So what I did was I just updated the app, then copied it back
onto the server.
Click to expand...

VS.NET 8.0 (aka VS.NET 2005) works with .NET Framework 2.0
VS.NET 7.1 (aka VS.NET 2003) works with .NET Framework 1.1

It means that once you convert the project into new "format" you will
not be able to open it in the previous version of VS.NET.
 
Back
Top