Last post Jan 18, 2008 02:43 PM by alisonlu
Dec 03, 2007 07:14 PM|Rasetti|LINK
I have a WDP that worked flawessly in VS2005 (still does!)
Today, after installing the WDP CTP for VS 2008, I tried to build the same project and I found that, every time I would do it, the following .dlls got copied to the bin folder and, then, deployed to the target's bin:
System.Data, System.Data.OracleClient, System.Enterprise, System.Enterprise. Transactions and System.Web
When I build and run the project locally hitting the "play" button, it doesn't happens.
Obviously these files shouldn't be there, so I'm wondering what the problem could be. Any ideas?
My web site is targeting .NET 2.0 and I'm running VS 2008 Professional on Windows Vista.
Dec 10, 2007 11:43 AM|rubikcube|LINK
I've got the same issue at the moment, along with the fact that my web.config sections aren't being replaced.
Dec 10, 2007 02:52 PM|Rasetti|LINK
I've posted the issue as a comment in Vishal's blog, but there is no follow-up yet, let's see what happens....
Dec 12, 2007 09:58 PM|alisonlu|LINK
Hi rubikcube, as I told Juan on the blog, the web.config replacement is a known issue that we are fixing.
Thanks Juan for the additional info. Is it possible for one (or both) of you to send me your project? You can send me the zip file using alisonlu at microsoft. I'm not too sure why individual dlls are appearing in your output folder and are not being
merged. Does this also happen to your output when you try Publish Web?
Dec 12, 2007 10:09 PM|Rasetti|LINK
Hi Alison, thanks for the super quick follow up!
If I build the project from VS or if I just Publish it, it works (no dlls added). That only happens when the project is compiled using WDP 2008 CTP.
I'm more than happy to send you he project, just let me know if an 8 mb zip file is ok for your email
Dec 13, 2007 02:24 PM|alisonlu|LINK
Hi Juan, yes, it will be no problem at all. Hopefully we can get to the bottom of this. Thanks!
Dec 13, 2007 03:40 PM|Rasetti|LINK
I just sent you the email, I hope you can reproduce the issue and find something there,
Dec 13, 2007 04:55 PM|alisonlu|LINK
Thanks Juan, I have it in my Inbox now. I hope I can repro too, and I'll let you know if I need anything else.
Dec 16, 2007 08:58 PM|hblakeslee|LINK
Did this ever get resolved? I am experiencing the same problem. Thanks in advance.
Dec 17, 2007 02:27 PM|Rasetti|LINK
I still have the same problem.
However, I sent a project to the webdevtools team for them to try to reproduce the issue, I hope that they can do it and come back with a fix.
Dec 17, 2007 08:30 PM|hblakeslee|LINK
Thanks for the reply Juan. I did a little more testing and now I am pretty sure the problem is caused by AJAX 1.0. Here is what I did:
1. Created a brand new "file system" web project based on the 2.0 framework.
2. Added a new web deployment project to the solution.
3. Compiled the solution in "Release" and checked the release\bin folder. Everything looks fine. Only 1 dll (as expected).
4. Added AJAX 1.0 to my solution by updating my web config file and adding a reference to the ajaxcontroltoolkit.dll.
Now when I compile, the additional DLLs appear in my release\bin folder. So it looks like the additional DLLs are perhaps detected dependencies of the AJAX toolkit DLL???
I have the above solution all zipped up if anyone needs it. Let me know if I'm doing something wrong. Thanks!
Dec 17, 2007 09:03 PM|Rasetti|LINK
Hal, very interesting finding indeed and I tell you why:
Another "quirk" I found when I tried WDP 2008, was that if I was using the AjaxToolkit ToolkitScriptManager instead of the standard Ajax ScriptManager, I would get lots of "undefined" errors on Toolkit enabled pages.
Just changing it back to the normal Ajax ScriptManager would fix it, but I was wondering why compling the project with WDP would break that functionality. I didn't pay much attention then, but now your comment gets me back there.
Now I'm wondering if there is some kind of strange interdependency / versioning conflict here, that breaks the AjaxToolkit functionality and brings all those dll's. I'm going to send Alison an email just to make sure they read these last posts.
Dec 17, 2007 09:27 PM|alisonlu|LINK
Thanks Hal for your repro steps...it definitely narrowed down the problem for us! Also, a big thanks to everyone here for bringing this to our attention.
Hal, it doesn't look like you did anything wrong. I have just repro'd the problem on our side and should have enough information now to find a fix to this. I appreciate everyone's patience in working with me and sending me extra info. I will keep everyone
posted if there is an easy workaround.
Dec 27, 2007 10:59 PM|hblakeslee|LINK
Any news on a fix or workaround? TIA.
Dec 27, 2007 11:07 PM|alisonlu|LINK
Not yet. Many members of the team have been out for the holidays, but we have not forgotten about this issue.
Jan 18, 2008 02:43 PM|alisonlu|LINK
I'm just here to update everyone. The bugs with config replacement and extra dlls in the bin folder have both been fixed. If you are interested in trying out if our current build works for you, please see this post: