You searched for the word(s): userid:631369

More Search Options

RSS Available

• Re: Error After Targeting .NET Framework 3.5: Child Nodes Not Allowed

  Well, Microsoft closed the case last week ... no resolution. They didn't ever come back and suggest any other changes or stuff to try. I guess if you are reading this thread that is bad news. After I reinstalled Windows and all my programs, VS built the same exact files without error. Don't know what to say. I hate issues like this where you never really figure out what was causing the problem.

  Posted to Visual Studio 2008 (Forum) by Cal Zant on 2/24/2008

• Re: Error After Targeting .NET Framework 3.5: Child Nodes Not Allowed

  I talked with the support team for VS 2008 yesterday, and they suggested a fix ... but unfortunately it didn't work. They thought that somehow the C:\Windows\SysWOW64\inetsrv\Microsoft.Web.Administration.dll had been corrupted or was out of sync with the rest of the dlls, so they asked me to replace it with a copy of the same file from a machine that wasn't having this issue. I did that, and I still got the same error. Since it did take Microsoft a couple days to get back to me from my original

  Posted to Visual Studio 2008 (Forum) by Cal Zant on 2/14/2008

• Re: Error After Targeting .NET Framework 3.5: Child Nodes Not Allowed

  I opened a phone support case with Microsoft, and they first sent me to the general level 1 support-type people then the developer support, then the ASP.NET Team, then the Visual Studio & .NET Framework setup people, then on to the Visual Studio team ... and after a 5 hour support call that is still where it is. I believe some members of the Vista or Visual Studio team are reviewing some sfc log files from my machine. I will update this post when/if we figure out what is going on. But one thing

  Posted to Visual Studio 2008 (Forum) by Cal Zant on 2/5/2008

• Re: Error After Targeting .NET Framework 3.5: Child Nodes Not Allowed

  Yeah, I appreciate your reply ... but I have already seen that post. Really since this is a compile-time error, I don't think it has anything to do with IIS. In fact, since I am kind of at a stand still until I get this figured out, yesterday I uninstalled Visual Studio, the .NET Framework, IIS, and anything else on my machine that could be remotely related. I then reinstalled everything (except IIS), got all of the possible Windows Updates (including the ones on the VS DVD) ... and it is still

  Posted to Visual Studio 2008 (Forum) by Cal Zant on 2/5/2008

• Error After Targeting .NET Framework 3.5: Child Nodes Not Allowed

  I have recently switched over to VS 2008, and at first I was just continuing to target the 2.0 framework. I thought I would try to make the switch to 3.5, and changed all the projects in my solution to target it. It modified the web.configs of the sites to include a system.codedom section. The problem is when I go to build the solution now, I get a compile-time error saying "Child nodes are not allowed" ... which points to that new section in the web.configs: < system.codedom > <

  Posted to Visual Studio 2008 (Forum) by Cal Zant on 2/4/2008
  Filed under: Vista, vista 64-bit, vista vs2008, Vistaisual Studio 2008, Visual Studio 2008, visual Studio 2008 custom provider bug, vs 2008, .NET, .NET 3.5, .net framework 3.5, 3.5, ASP.NET 3.5, converting 2.0 to 3.5 iis 7, iis7

• Re: Reorder List & ObjectDataSource

  Sorry, I should have mentioned that I already tried that, because I thought the same thing. In fact I had to do the same thing on the one that I got working to fix an issue with it. But on this one it never gets to the breakpoint I have set in the update method, and never catches any server-side exceptions. Any other ideas?

  Posted to ASP.NET AJAX Control Toolkit (Forum) by Cal Zant on 3/7/2007

• Reorder List & ObjectDataSource

  I am trying to use the ReorderList control with an ObjectDataSource, and have it working on one page. It is so intuitive and user-friendly that I wanted to make another page to sort a different type of object. Its frustrating because the code looks almost identical on the pages, but I get the "Reorder Failed" on the new one ... and the other one updates as expected. My code is pretty straight-forward, so I will list it here. Any ideas would be appreciated. <ajaxToolkit:ReorderList ID="rlChecklists

  Posted to ASP.NET AJAX Control Toolkit (Forum) by Cal Zant on 3/7/2007

• Re: Issue With New AutoCompleteExtender

  It appears that it is working now, however it wasn't when I originally posted my message in IE 7. I will check it in my application again and see if it is working now.

  Posted to ASP.NET AJAX Control Toolkit (Forum) by Cal Zant on 2/21/2007

• Re: Issue With New AutoCompleteExtender

  If the path or proxy was wrong, the cascading drown down that uses the same reference and is on the same page wouldn't be able to recieve information from the method that it calls in that same web service. So I don't think the client proxy is the issue. Any other ideas?

  Posted to ASP.NET AJAX Control Toolkit (Forum) by Cal Zant on 2/14/2007

• Issue With New AutoCompleteExtender

  I am trying to use the AutoCompleteExtender, and noticed that it was moved out of the ASP.NET Ajax functionality and into the AJAX Control Toolkit. I am having a little trouble getting it implemented, even though it looks like I have everything in place. I noticed the demo of this control at http://ajax.asp.net/ajaxtoolkit/AutoComplete/AutoComplete.aspx doesn't appear to be working either, so I figured it was probably an issue with the actual control code and might not be the way I am using it. I

  Posted to ASP.NET AJAX Control Toolkit (Forum) by Cal Zant on 2/9/2007