pulling hair out
-
I think I am going nuts over this .NET thing. As far as I can tell, the MSDN documentation is just wrong. There is no such thing as a listbox.refresh method, nor is there such a thing as a listbox.multicolumns property, as just two examples. The docs say there is, but VS.NET gives me a compile error. I have this wretched,sinking feeling that my confusion lies in the difference between ASP.NET programming and Visual Basic.NET programming. Is it possible that listobx behaves two completely different ways in each? Is it possible that MSDN doesn't bother to clarify the language context of its instructions? Is it possible that not being able to filter results for one vs. the other (VB.NET vs. ASP.NET) in searches is an awful idea? I am very frustrated. ________________________________________________________________________ Dave Y10K bug! Let's not get caught with our pants down **AGAIN**! (DC 02002)
-
I think I am going nuts over this .NET thing. As far as I can tell, the MSDN documentation is just wrong. There is no such thing as a listbox.refresh method, nor is there such a thing as a listbox.multicolumns property, as just two examples. The docs say there is, but VS.NET gives me a compile error. I have this wretched,sinking feeling that my confusion lies in the difference between ASP.NET programming and Visual Basic.NET programming. Is it possible that listobx behaves two completely different ways in each? Is it possible that MSDN doesn't bother to clarify the language context of its instructions? Is it possible that not being able to filter results for one vs. the other (VB.NET vs. ASP.NET) in searches is an awful idea? I am very frustrated. ________________________________________________________________________ Dave Y10K bug! Let's not get caught with our pants down **AGAIN**! (DC 02002)
DaveC426913 wrote: Is it possible that listobx behaves two completely different ways in each Yes, they do behave differently. The Windows.Forms version supports a
.Refresh()method, where the WebForms version doesn't. The .Refresh method just redrwas the control and it's contents in Windows Form. This can't be done on a browser version. The browser version is just a wrapper for an INPUT tag in HTML. ListBox[^] control in ASP.NET, or WebForms. ListBox[^] control in Windows Forms. If you scroll up the navigation pane on the left, you'll see which namespace these controls are under.System.Windows.Formscontains all the standard Windows Forms controls, while all the standard ASP.NET, or WebForms, controls are underSystem.Web.UI.WebControls. RageInTheMachine9532 "...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome -
DaveC426913 wrote: Is it possible that listobx behaves two completely different ways in each Yes, they do behave differently. The Windows.Forms version supports a
.Refresh()method, where the WebForms version doesn't. The .Refresh method just redrwas the control and it's contents in Windows Form. This can't be done on a browser version. The browser version is just a wrapper for an INPUT tag in HTML. ListBox[^] control in ASP.NET, or WebForms. ListBox[^] control in Windows Forms. If you scroll up the navigation pane on the left, you'll see which namespace these controls are under.System.Windows.Formscontains all the standard Windows Forms controls, while all the standard ASP.NET, or WebForms, controls are underSystem.Web.UI.WebControls. RageInTheMachine9532 "...a pungent, ghastly, stinky piece of cheese!" -- The Roaming GnomeArg. OK, I'm giving up on all the OledbConnect and SQLConnect examples, and sticking with ADO. ________________________________________________________________________ Dave Y10K bug! Let's not get caught with our pants down **AGAIN**! (DC 02002)
-
I think I am going nuts over this .NET thing. As far as I can tell, the MSDN documentation is just wrong. There is no such thing as a listbox.refresh method, nor is there such a thing as a listbox.multicolumns property, as just two examples. The docs say there is, but VS.NET gives me a compile error. I have this wretched,sinking feeling that my confusion lies in the difference between ASP.NET programming and Visual Basic.NET programming. Is it possible that listobx behaves two completely different ways in each? Is it possible that MSDN doesn't bother to clarify the language context of its instructions? Is it possible that not being able to filter results for one vs. the other (VB.NET vs. ASP.NET) in searches is an awful idea? I am very frustrated. ________________________________________________________________________ Dave Y10K bug! Let's not get caught with our pants down **AGAIN**! (DC 02002)
DaveC426913 wrote: Is it possible that MSDN doesn't bother to clarify the language context of its instructions? No, it tells you at the top, when it tells you the namespace of the control you're reading about. Christian Graus - Microsoft MVP - C++
-
Arg. OK, I'm giving up on all the OledbConnect and SQLConnect examples, and sticking with ADO. ________________________________________________________________________ Dave Y10K bug! Let's not get caught with our pants down **AGAIN**! (DC 02002)
:confused::confused::confused::confused::confused::confused::confused: OleDbConnect and SqlConnect aren't part of the .NET Base Class Library or ADO.NET. Where did these come from? And, they don't have anything to do with your original post, so I'm afraid I'm lost. RageInTheMachine9532 "...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome
-
:confused::confused::confused::confused::confused::confused::confused: OleDbConnect and SqlConnect aren't part of the .NET Base Class Library or ADO.NET. Where did these come from? And, they don't have anything to do with your original post, so I'm afraid I'm lost. RageInTheMachine9532 "...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome
"OleDbConnect and SqlConnect aren't part of the .NET Base Class Library or ADO.NET. Where did these come from?" They are controls available to me it VS.NET when I am designing ASP.NET or VB.NET apps, and used in the tutorials and samples I'm reading in these ASP.NET and VB.NET books and at MSDN. I'm sure if I read the books and MSDN website page by page, it will explain the difference. I guess I can't just presume that prior VB and ASP knowledge would have saved me from this confusion. ________________________________________________________________________ Dave Y10K bug! Let's not get caught with our pants down **AGAIN**! (DC 02002)
-
"OleDbConnect and SqlConnect aren't part of the .NET Base Class Library or ADO.NET. Where did these come from?" They are controls available to me it VS.NET when I am designing ASP.NET or VB.NET apps, and used in the tutorials and samples I'm reading in these ASP.NET and VB.NET books and at MSDN. I'm sure if I read the books and MSDN website page by page, it will explain the difference. I guess I can't just presume that prior VB and ASP knowledge would have saved me from this confusion. ________________________________________________________________________ Dave Y10K bug! Let's not get caught with our pants down **AGAIN**! (DC 02002)
OleDbConnection and SqlConnection are objects, but not OleDbConnect or SqlConnect. I never use the database controls in the ToolBox. I always code my database stuff by hand. It gives greater control and you don't have to worry about code being generated that you can't see without going into the "Windows Form Designed generated code" region. Do it by hand and everything is in one place. ADO.NET is strickley for database access. ASP.NET is a server-side HTML generation technology. RageInTheMachine9532 "...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome
-
OleDbConnection and SqlConnection are objects, but not OleDbConnect or SqlConnect. I never use the database controls in the ToolBox. I always code my database stuff by hand. It gives greater control and you don't have to worry about code being generated that you can't see without going into the "Windows Form Designed generated code" region. Do it by hand and everything is in one place. ADO.NET is strickley for database access. ASP.NET is a server-side HTML generation technology. RageInTheMachine9532 "...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome
Forgive me if this is turning into a .NET tutorial, but it is very helpful to me... So, does that mean all your code is on the .ASP page, not in the codebehind page? Is there *anything* on the codebehind page? I confess I am confused about the relationship between the ASP page and the codebehind page in terms of what exists on each. I tried mapping one to the other, but some parts are there and some aren't. Is it possible to code ASP.NET pages without any need for a codebehind page? ________________________________________________________________________ Dave Y10K bug! Let's not get caught with our pants down **AGAIN**! (DC 02002)
-
Forgive me if this is turning into a .NET tutorial, but it is very helpful to me... So, does that mean all your code is on the .ASP page, not in the codebehind page? Is there *anything* on the codebehind page? I confess I am confused about the relationship between the ASP page and the codebehind page in terms of what exists on each. I tried mapping one to the other, but some parts are there and some aren't. Is it possible to code ASP.NET pages without any need for a codebehind page? ________________________________________________________________________ Dave Y10K bug! Let's not get caught with our pants down **AGAIN**! (DC 02002)
Everything VB.NET is in the codebehind file. Everything HTML is in the .apsx file. The VB.NET code controls what happens when you use the controls on the HTML page. It's very similar to what's going on in Windows Forms. You see the Designer that lets you place the controls on a form and the "codebehind" that lets you attach code to the control's events, like "click". RageInTheMachine9532 "...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome
-
Everything VB.NET is in the codebehind file. Everything HTML is in the .apsx file. The VB.NET code controls what happens when you use the controls on the HTML page. It's very similar to what's going on in Windows Forms. You see the Designer that lets you place the controls on a form and the "codebehind" that lets you attach code to the control's events, like "click". RageInTheMachine9532 "...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome
I see Visual Basic code in aspx pages in the examples. Is this not generated from the code window? Also, when I write Visual Basic in the code window, it creates HTML/ASP/VB in the HTML page. Are you saying that if I write everything in the HTML page, there will be nothing (or at least, nothing of consequence) in the codebehind file? I guess I should try this so I understand it better, it just seems like I'm throwing away many of the features of Visual Studio. Is it possible that the relationship between Visual Studio and html pages is equivalent to something like FrontPage and html pages? i.e. Frontpage is easier for designers, but it blows as far as writing clean code. I never use WYSYWIG HTML editors - I always use Homesite (which doesn't mangle code). ________________________________________________________________________ Dave Y10K bug! Let's not get caught with our pants down **AGAIN**! (DC 02002)