|
Subject:
|
VS 2003 developer needs help with 2005
|
|
Posted By:
|
DingoAce10
|
Post Date:
|
12/12/2005 12:29:03 PM
|
What's up all,
I just recently upgraded to VS.NET 2005 and I am getting SO frustrated with trying to deploy/build a web site in it.
I am used to creating a new "web project" in 2003, clicking the build option, have it create one .dll file...Copying my .aspx and the one .dll file down to my IIS server and having it work.
I know I can use that "publish web site" option and choose the directory to publish to...but that creates to much of a mess.
I downloaded the Web Deployment addon from MS, and that will create one .dll file for me, but everytime I move the files to my IIS server, I get a parsing error that it can't find the dll file that VS created.
What's the deal?? I am about 3 secs away from uninstalling 2005 and go back to 2003! :-)
Thanks very much in advance!
|
|
Reply By:
|
Imar
|
Reply Date:
|
12/12/2005 12:59:30 PM
|
Well, I guess my answer comes too late then.... ;-)
Anyway, did you read the documentation that comes with the web deployment projects tool? What deployment model do you use?
Also, what mechanism do you use to publish your site? FTP is not supported with web deployment projects.
Finally, is the error message right? Is there no DLL file in your BIN folder after you successfully ran web deployment projects?
Imar
---------------------------------------
Imar Spaanjaars
Everyone is unique, except for me.
|
|
Reply By:
|
DingoAce10
|
Reply Date:
|
12/12/2005 1:07:04 PM
|
Hi Imar,
I don't see the doc that came with the add on, but I have read through this, which seems pretty straight forward:
http://weblogs.asp.net/scottgu/archive/2005/11/06/429723.aspx
Yes the file is in the bin directory of the site.
I am building the site in a different directory and then just copying the need files down to the web site. Always gives me the parsing error saying:
"Could not load the assembly 'nsWFDeployment'. Make sure that it is compiled before accessing the page."
I am using Windows 2003 server for my OS...Do I need to set an environment variable to look in the bin dir or something?
Thanks!
|
|
Reply By:
|
Imar
|
Reply Date:
|
12/12/2005 1:27:40 PM
|
By design, .NET looks in the Bin folder if a website has been marked as an application.
is that the case with your remote app? Are you sure it's not just a folder, but that it has been changed in to an Application under IIS?
The docs for the web projects can be downloaded here: http://msdn.microsoft.com/asp.net/reference/infrastructure/wdp/default.aspx
HtH,
Imar
---------------------------------------
Imar Spaanjaars
Everyone is unique, except for me.
|
|
Reply By:
|
DingoAce10
|
Reply Date:
|
12/12/2005 1:46:45 PM
|
Hi Imar,
Ok, I didn't have to do that before, but I make the bin dir on my wwwroot folder and application from within IIS manager, still nothing.
THanks!
Gary
|
|
Reply By:
|
Imar
|
Reply Date:
|
12/12/2005 4:35:05 PM
|
You shouldn't make the Bin folder an application, but the Bin's parent folder.
So if you have this:
C:\Inetpub\wwwroot\MyApplication and
C:\Inetpub\wwwroot\MyApplication\Bin
then C:\Inetpub\wwwroot\MyApplication should be marked as an app in IIS, with the Bin folder belonging to that app.
Also, make sure that the account used by the webserver has the necessary permissions....
HtH,
Imar
---------------------------------------
Imar Spaanjaars
Everyone is unique, except for me.---------------------------------------
Imar Spaanjaars
Everyone is unique, except for me.
|
|
Reply By:
|
DingoAce10
|
Reply Date:
|
12/13/2005 10:50:37 AM
|
Thanks again Imar...
Right now, I am just playing around right now with a new app, so I am just putting my .aspx pages in wwwroot folder and putting my .dll files in the bin folder underneath the wwwroot folder.
c:\inetpub\wwwroot
c:\inetpub\wwwroot\bin
With 2003 I usually just had 1 bin folder for all of my .dll files for all of the .aspx pages.
So you are saying that you put a bin subfolder in all of your application folders?
Thanks again!
|
|
Reply By:
|
Imar
|
Reply Date:
|
12/14/2005 1:22:10 PM
|
Hi Gary,
It all depends on what you configured to be an application.
If c:\inetpub\wwwroot is marked as an application then c:\inetpub\wwwroot\bin is the place to put the DLL files for that site.
If c:\inetpub\wwwroot\App1 and c:\inetpub\wwwroot\App2 are also marked as applications, their DLLs should be stored in c:\inetpub\wwwroot\App1\bin and c:\inetpub\wwwroot\App2\bin respectively....
HtH,
Imar
---------------------------------------
Imar Spaanjaars
Everyone is unique, except for me.
|
|
Reply By:
|
DingoAce10
|
Reply Date:
|
12/14/2005 1:47:33 PM
|
Hi Imar,
Thanks for the info!
Is that new? I never had to do that when using 2000 server with VS 2003?
I just put all of my DLL files in the bin dir and could put my aspx files in any directory and it would just refer to the wwwroot\bin folder for all code-behind files.
I never had to specifically make the wwwroot folder it's own application.
I did just notice that the "aspnet_client" folder is not under my site wwwroot folder so that might be my problem also.
Thanks!
Gary
|
|
Reply By:
|
Imar
|
Reply Date:
|
12/14/2005 2:05:43 PM
|
No, that's not new. In ASP.NET 1.1, each app had its own Bin folder as well.
However, the Default Website (by default at C:\Inetpub\wwwroot) is already an application when you have IIS installed.
You can also have different folders beneath wwwroot that share the same parent application and Bin folder. However, they would never be a separate app; e.g. those subfolders all share the same session and application state for example.
Be aware that you may need to configure IIS to use .NET 2. When you install IIS on a machine with the 1.1 framework, it doesn't update the sites to use v2. So, by default, sites will still run under 1.x.
Although at registration time you do get the aspnet_client folder, I don't think you need it anymore. The necessary files are streamed from the V2 assemblies automatically. Look at the source in the browser of an ASP.NET 2.0 page that uses validation and you'll see what I mean.
Imar
---------------------------------------
Imar Spaanjaars
Everyone is unique, except for me.
While typing this post, I was listening to: Jennifers Body by Hole (Track 5 from the album: Live Through This) What's This?
|
|
Reply By:
|
DingoAce10
|
Reply Date:
|
12/14/2005 2:31:11 PM
|
Thanks Imar,
I am using 2003 server as my OS and did the "manage server" for an application server which installs the nessesary files for .Net and the VS 2005 installed the nessesary files for v2.0.
How would I tell if my IIS is still using 1.1?
BTW, I don't use the default site...usually create a whole other folder structure for security reasons.
Thanks!
Gary
|
|
Reply By:
|
DingoAce10
|
Reply Date:
|
12/14/2005 2:34:03 PM
|
Sorry Imar, forget part of that last post...I found where to set it to use v2.0.
Thanks!
Gary
|
|
Reply By:
|
DingoAce10
|
Reply Date:
|
12/14/2005 2:44:34 PM
|
Hi again Imar,
Ok, that did it...When you create a new site, the application is automatically created on the root dir. So that is why I didn't understand what you were saying..
Otherwise...What fixed it what that, under the ASP.NET tab I set it to v2.0 and now it is running like I want :-)
YEAH!!!!!
That ASP.NET tab is new to me(was previously using IIS 5.0, which doesn't have that)...So I didn't know to go in there and set it.
Thank VERY MUCH for being so help and patiant!!!
Gary
|
|
Reply By:
|
Imar
|
Reply Date:
|
12/14/2005 2:51:28 PM
|
You're welcome. Glad it's all working now.
The ASP.NET tab is not new to IIS 6, but new to .NET 2.0. When you install the .NET 2.0 Framework on a machine with IIS, you get that tab to allow you to easily switch to another version of the framework. You get it on Win 2K as well. Previously, you had to use command line or third party tools.
Cheers,
Imar
---------------------------------------
Imar Spaanjaars
Everyone is unique, except for me.
|
|
Reply By:
|
DingoAce10
|
Reply Date:
|
12/14/2005 3:01:02 PM
|
Gotcha! First time installing 2.0, maybe that is why I never saw it before.
Now getting more used to VS 2005 and now that I have that all straightened out, I like it even more.
Thanks so much!
|
