I'm note sure about the node expanding problem but I think the two scroll bars are caused because of CSS inheritance. All child elements of the Panel will inherit the overflow:scroll property (meaning the TreeView container div). I think thats how it works anyway, not 100% sure.
It was very much helpful, I have a problem with the values on x- axis.
I need to display the DateTime parameter here.Such as data for 10 days. I am not able to control that value. I mean on the graph I need same time to be desplayed on each day, Secondly I am not able to control the data that is displayed.
I have more of a design type of question.
Can anyone tell me if it is possible to :
I have a win 32 dll and a C# web service. Instead of creating a c# client, i would like to use my win 32 dll as the client. I use this dll for other things that are all file related. Is it possible for me to make the dll the client and to be able to call the c# web service and send and receive data from it? If so, does anyone have any examples of how to turn an already existing win 32 dll into a client accessing a c# web service?
With VisualStudio.Net, i'm using an installer class with a custom action
on my setup project to ask the user a serial number. A "Textboxes"
dialog on the "user interface" provides the serial number string to an
overrided version of then install procedure, inside my installer class.
My problem is that the install sub is able to verify the serial number
entered, but then i can't stop/cancel the installation procedure.
When I tried to convert to Windows app to Web Application i get an error saying
"Error 4 'ASP.satori_recherche_aspx.GetTypeHashCode()': no suitable method found to override c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\websatoricontact\5f44883e\69c9d6e5\App_Web_ujyjcgyh.8.cs 3177
I'm pretty sure you can't just create a new form (Page) via its constructor, only the ASP.NET runtime will create Page objects during the request lifecycle. By the looks of things, you're trying to show another dialogue in the new form. Web applications work completely differently to WinForms apps, you'll find it very difficult to try and convert the UI code. I would suggest you try keeping as much business logic as possible and start the aspx (UI) coding from scratch since the code is totally different from WinForms.