I guess I stumped the crew with my little build-quitting problem, is Not the web-deployment add-in meant for real-world data-rendering website projects - with a standard CommonRoutines file, it just seems like common sense, if the
website will build, AND publish, then the little null-reference exception and CLS-error warnings should carry over in being able to ignore them while building the website-merge assembly, right?
Is this a further bugfix we'll have to wait for in order to be able to deploy our product-upgrade written to take adv. of all the great 2.0 framework enhancements in the same manner as we've done previously with 2003? (one single
installation assembly)
Some sort of progress report, if not a viable workaround, would be greatly appreciated.
sean6106
Member
25 Points
5 Posts
Problem with aspnet_merge.exe
Jun 07, 2006 02:23 PM|LINK
I guess I stumped the crew with my little build-quitting problem, is Not the web-deployment add-in meant for real-world data-rendering website projects - with a standard CommonRoutines file, it just seems like common sense, if the website will build, AND publish, then the little null-reference exception and CLS-error warnings should carry over in being able to ignore them while building the website-merge assembly, right?
Is this a further bugfix we'll have to wait for in order to be able to deploy our product-upgrade written to take adv. of all the great 2.0 framework enhancements in the same manner as we've done previously with 2003? (one single installation assembly)
Some sort of progress report, if not a viable workaround, would be greatly appreciated.
Thanks,