Last post Jan 12, 2010 09:01 PM by teebon
Aug 01, 2009 03:00 PM|HeuDotNet|LINK
When i try to build my Web Application project using the Web Deployment Projects the dll's aren't splitting into seperate asemblys as i have set it to.
My output look like this:
========== Build: 2 succeeded or up-to-date, 0 failed, 1 skipped ==========
As you see there is an error, but i'm only getting this when i build it in a Web Application Project. If i just create a Website Procjet it works fine.
Thanks in advance
Aug 02, 2009 06:07 AM|GillouX|LINK
first of all, it's not an error but just a warning.
to fix it, you should make the following :
right click on the web deployment project -> properties and in the Output Assemblies : thick the option "Create a separate assembly for each page and control output"
hope it helps
Aug 02, 2009 09:27 AM|HeuDotNet|LINK
Thanks for you reply.
I tryed to do as you suggested but it's sill merging the project into one dll in the bin folder.
I would like to use the option: Merge each individual folder output to its own assembly.
Cause that looked like what I was looking for to achieve with dll's splitted into different folders like Project.Folder.Item.dll.
As i would like to update some dll's this seems like a nice approach.
The fact that it doesn't work is making my head explode cause it should work with Web Applications aswell and not just Website Projects.
It feels like i have tryed everything, but i hope there is a solution out there.
Aug 02, 2009 09:37 AM|HeuDotNet|LINK
If i untick "Allow this precompiled site to be updateable" then it works except i
do want it to be updateable.
I don't want all those .compiled files.
Any ideas why it's working like this and not when it's ticked?
Aug 02, 2009 09:40 AM|GillouX|LINK
why do you need to make a web application and not a web site project ?
Aug 02, 2009 11:46 AM|HeuDotNet|LINK
The problem is that it is allready a Web Application with a lot of code.
What pros and cons are there for using Web Application versus Website Project?
I guess it wouldn't be that hard to convert it.
Aug 02, 2009 12:37 PM|GillouX|LINK
here is an article which covers this topic
the conclusion : give up on the website project and use the web application.
about converting your website to web app
they are plenty of website covering this
here is one of them :
Aug 02, 2009 07:05 PM|HeuDotNet|LINK
My problem is that i'm allready using the "Web Application Project", but the Web Deployment Project doesn't work (for some reason)
So i have now converted the whole project to a "Web Site" (by copying code, so much fun
) and now the Web Deployment Project does work and does the job as it should.
I kinda like the "Web Application Project" better as i'm more used to it but i don't really see the big difference, i don't know, what do you think?
Jan 12, 2010 09:01 PM|teebon|LINK
I'm currently facing exactly the same issue as I need to use Web Application and would want to compile multiple assemblies based on their respective folder.
May I know anyone out there has a solution or know whether this is covered in Visual Studio 2010?