asp.net 2.0 in VS '05 to generate dll's & not exe's?

[Jason Shohet]

I'm trying to figure out *why* VS.NET is creating exe's for us instead of
dll's now...
And how we can set it back to create dll's during the build.

TY
jason shohet

 

[Guest]

What kind of project are you using? Windows Forms?

 

[Jason Shohet]

asp.net 2.0 project, not windows forms. Using beta 1.
When we go to 'build' in the menu, it does a build. I went to look in the
'data' & in the 'code' directories, and don't see any dll's / exe's or
anything. I'm not sure what is actually happening when I do build, where &
what is being built So we have no way of deploying... Also, I know
about the option to make exe's, but not sure where that option is set in the
menu. Sorry for the newbie questions , thanks Ken!

Jason Shohet

 

[CJ Taylor]

asp.net 2.0 project, not windows forms. Using beta 1.

When we go to 'build' in the menu, it does a build. I went to look in the
'data' & in the 'code' directories, and don't see any dll's / exe's or
anything. I'm not sure what is actually happening when I do build, where &
what is being built So we have no way of deploying... Also, I know
about the option to make exe's, but not sure where that option is set in the
menu. Sorry for the newbie questions , thanks Ken!

It will still be in the /bin directory... Until Beta2/R1 when its put into
the Application_Assemblies/ directory...

 

[Jason Shohet]

hmmm, we don't see a bin directory. The project has aspx & a .cs
codebehind. We did a build. There's a data directory, no bin directory...

 

[Jason Shohet]

And whats wierder, when we go to 'publish' (i did that thinking ok, if i
can't find the dll's manually, lets see if asp.net 2.0 lets me publish to a
site), I published the site to a place in wwwroot. But looking at the
pages, they all have wierd names, with .compiled extensions and other
wierd extensions. And when I browse to the site, I get this message:

This is a marker file generated by the precompilation tool, and should not
be deleted!

So I'm kinda lost with what MS is trying to do here. Its kinda like Toyota
messing around with a Toyota Camry by installing air bags on the roof....
I keep scratching my head here, trying to figure out where my dll's are and
how to deploy

TY again

 

[CJ Taylor]

In the project explorer? If you want to see a bin directory go to Show All
Files at the top of the solution explorer.

Otherwise, just browse out to that directory with Windows Explorer.

Finally, as for deployment, VS2005 has some really sweet deployment options
including FTP... Which is great (especially precompiled webs!)

HTH,
CJ

 

[CJ Taylor]

It's kinda like Microsoft's own type of Obfusication tool. If you look at
your aspx/ascx files you'll notice they all reference these weird names...

You did a precompiled web, one of the great new features in Whidbey.
However, if you wan tto change it, you have to completly recompile the web
(which is actually *better* to do because it forces you to test locally...
rather than on a production server.)..

Weird how its all different DLL names huh? threw me off too the first time.

-CJ

 

[Jason Shohet]

So if you publish it, VS.net automatically does a 'precompiled' web. How do
you move this thing to production I'm wondering. What does precompiled mean
to me... I mean, you can't test out the site without getting that
'marker' message.... so what is the benefit. I'm missing something here
obviously.

I've read briefly msdn's articles about the 3 different ways to deploy
(aspx + dll's, exe's, and one other 3rd way) but don't see any practical
"here's what to select off the menu" instructions so I can try out my app

TY CJ!

 

[CJ Taylor]

I only have it available at home, so I'm kinda grasping to remember
*exactly* how its done.

Alright, a precompiled web puts *all* code into the DLL's creating a certain
level of security I suppose. If you look at the aspx pages you'll see that
they just reference the file (If I remember correctly). No HTML, no
nothing, just a directive.

The benefit, supposidly faster execution (kinda like 1.x) because it doesn't
have to do any JIT compiling..I've only read this, haven't really tested it.

As far as deploying, just FTP it up to the site, your good to go.. it takes
care of the rest. No more FP2000/2002.

 

[Jason Shohet]

CJ,
so lets say I go thru and do it this way. Can you 'hold my hand' a bit and
explain how to deploy using this scenario. ie, I've done the precompiled
web. Whats the next step to deploy it...

(I can't even find where to set these deployment options in the new
V.Studio -- all i see are articles stating what can be done, w/o saying how
to do it lol)

 

[Jason Shohet]

sorry i just posted again b4 seeing your answer
ok if I FTP it to my site, its going to have exactly the same problem as it
does now, giving that "this page is a marker..." message right? I mean,
FTP'ing is just copying the site somewhere else. And right now that
precompiled site gives that wierd message and doesn't run. So I'm not sure
if just FTP'ing it somewhere else is going to change anything ? Maybe i'm
missing something here

TY

 

[CJ Taylor]

Ok, It's under WebSite/Copy Website in the express edition. I have a MSDN
Universal so I have the full blown version, which seems to have a few extra
features.

What is the error message you are getting upon deployment? I don't
understand.

BTW, no problem helping. We all start somewhere.

Also, your deployment server, it has .NET 2.0.xxx on it right? What kind of
server is it?

-CJ

 

[Jason Shohet]

CJ
ok got it. I found the copy website menu item and did it and all works
well. I like this copy utility much better -- yea FTP and all. sweet. But
I'm still lost on the below:

1. why does VS now default to store the site in a development folder
outside of wwwroot. ie, if I'm developing the site and its being stored in
c:\WEBSITES , what was wrong w/ wwwroot? When i hit debug, instead of
going to http://127.0.0.1 etc it goes to http://localhost:24329/mysite/
so I guess the site is still able to be run despite it being outside of
wwwroot. But i'm not sure why we're abandoning wwwroot.

2. I'm not sure what *publish* website is, compared to *copy*. Copy I
understand now. It works fine for me. Publish did the precompiled web,
which -- I can't see what use it is as of yet. When you browse to a
precompiled web you get that wierd message (on default.aspx) saying its just
a marker.... I understand the basic obsfuciation concept, hiding source
code during deployment -- but don't understand how it works in practice.

Thanks again -

 

[CJ Taylor]

CJ

ok got it. I found the copy website menu item and did it and all works
well. I like this copy utility much better -- yea FTP and all. sweet. But
I'm still lost on the below:

1. why does VS now default to store the site in a development folder
outside of wwwroot. ie, if I'm developing the site and its being stored in
c:\WEBSITES , what was wrong w/ wwwroot? When i hit debug, instead of
going to http://127.0.0.1 etc it goes to http://localhost:24329/mysite/

It's not *outside* of wwwroot, thats actually wwwroot/mysite.

also, if you do a ping localhost you'll see it comes up with 127.0.0.1 =)

As far as the port goes, I don't know exactly why that does it that way,
because it can't taken requests from any other machines but the local
machine. So seems like a little bit of overkill on MS's part, but hey,
that's them.

The fact that it builds the sub directories is because, ok, you develop Web
Site A, good... its under /wwwroot... however, say you have to develop Web
Site B. Which would overwrite A. BUt your still maintianing A... What do
you do? instead, just use the sub directories... This has its own issues
(like when purchasing templates! and the infamous ~/ issue... )

so I guess the site is still able to be run despite it being outside of
wwwroot. But i'm not sure why we're abandoning wwwroot.

2. I'm not sure what *publish* website is, compared to *copy*. Copy I
understand now. It works fine for me. Publish did the precompiled web,
which -- I can't see what use it is as of yet. When you browse to a
precompiled web you get that wierd message (on default.aspx) saying its just
a marker.... I understand the basic obsfuciation concept, hiding source
code during deployment -- but don't understand how it works in practice.

Havne't seen the marker thing so can't answer that... Sorry... the
precompiled web has its advantages, plenty of explanations on MSDN for that
on the different deployment models.

precompiled hides *everything* =)

 

[Jason Shohet]

ah got it. I've created tons of subwebs b4 but i always kept them in
wwwroot, never outside, thats why it threw me for a loop. Yea that was dumb
of me, I see that its still an IP address - from localhost - even if the
physical subweb folder is located out of wwwroot (which i forgot was
possible to do). Yea the port seems like overkill but what the heck.

I'll do more research on that publish / precompile thing, try to figure out
whats going on...
TY
jason shohet