I have tried creating a simple WHDG project using versions 2011.1.2116 and 2011.2.1019 of Infragistics ASP.NET (latest versions available at the time of this post) and have had to use the Windows Task Manager to repeatedly kill Visual Studio after 1-2 minutes of use. This seems to happen when closing the browser with debugging enabled, switching to design mode, and just about anything else.
My PC is running Windows 7 Ultimate 64 bit with the version latest security and other patches, Visual Studio 2010, version 4.0.30319 SP1Rel, and SQL Server 64 bit 2008 R2, version 10.50.2500.0. I have 16 GB RAM and lots of disk space.
This is incredibly frustrating. Any suggestions?
Hi,
I have been having this problem for a long time and just noticed this post. I once created a case about it, but couldn't figure out how to make a sample which would cause it to happen. The way I got around this issue was to assign the datasource to the WHDG in code behind and not in the markup. That stopped the freezing. The only problem was that I couldn't automatically build my grids from the datasource. But now, with the solution here of removing the update panel at design time, I can have the best of both worlds. Once I'm finished designing the grid, I can put the updatepanels back and assign datasource in code behind.
Hope this helps,
Ed
Hi All,
I am also having the same problem which is mentioned eariler in this post by Johnrosset and Luis.
Kindly help us to resolve the issue. This is an powerful control which we love to use but due to issue which prevails. Do the needful as earliest.
Thanks & Regards,
Godwin Jebakumar
Was there ever an official resolution for this issue? I'm having the same problem that johnrosset reported, witht he same workaround as a solution.
I'm running Visual Studio 2010, Version 10.0.40219.1 SP1Rel
Windows 7 Professional, Version 6.1 (Build 7601: SP1).
I have a WebHierarchicalDataGrid (version 12.2.20122.1007) inside of an updatepanel, and whenever I switch from Design to SourceView it freezes Visual Studio and I eventually have to kill it via Task Manager.
The problem goes away if I remove the Grid and it's DataSources from the UpdatePanel.
Thanks for you time.
Maya:
I think I may have determined the cause of the Visual Studio 2010 freezes. As soon as I removed the two lines and associated end tags shown below from the Default.aspx page in the project, the freezing stopped immediately and I can now edit/configure freely in design or split mode. Does this mean UpdatePanels should not be used with WHDG?
+++++
Lines removed from ASPX:
<asp:UpdatePanel ID="UpdatePanel1" runat="server">
<ContentTemplate>
Thanks for your efforts to follow-up with me. I'm afraid today is the first day I've had a chance to get back to this issue. In response to your questions, see my answers below:
1.Does this happen in any project containing the WHDG control? - Yes, I've tried creating several very simple projects using both .NET Framework 3.5 & 4.0 and as soon as I begin to configure the WHDG using the "smart tag" screens in design/split mode, VS 2010 freezes.
2.Does this happen in all browsers? - If I open the project and immediately launch the application without opening the form in design or split mode, it seems to work well in IE 9, FireFox 8 and Chrome 16. However, when I exit the browser and return to VS 2010 and begin work in design or split mode, VS freezes.
3.Does this happen with any other control? - I have another ASP.NET project which does not use the WHDG control and have had no real problems with it.
4.When did this issue start reproducing? - I have never used the WHDG before and wanted to test its functionality and speed. As noted above, the problem appears as soon as I begin to work on the WHDG control in VS using the design surface.
5.Does this reproduce in any other environment that you test the project in ? Yes - it happens on both my Win 7 64 bit desktop and laptop.
6.Have you tried to preinstall the controls? - I'm afraid I don't know how to do this.
7.Does the VS generate any kind of error message when it crashes? - "Crash" is probably not the best word to describe what happens - VS actually freezes and won't respond to keystrokes or mouse clicks. The Windows Task Manager shows the VS dev environment running at 12-13% CPU utilization and the amount of memory used by the application continues to grow until I end the VS task.