VB 2008 Why Are Static Variables Set Equal To 0 In The Declaration When 0 Would Be The Default Value Of The Numeric Variable
Apr 21, 2010
Why are static variables set equal to 0 in the declaration when 0 would be the default value of the numeric variable anyway when it's first declared? Not including the "=0" in the static declaration seems to work with no problem.
I have several classes that use a bunch of strings for directories, arguments, etc.
At the moment, they're all just declared globally within the class like so:
VB.NET Private str1 As String = "path" Private str2 As String = "path2" Private str3 As String = "arg"
To me, that looks awful and doesn't seem like the proper way of doing things. So, I was thinking, should I make a property for each string and then use a constructor to initialize them?
Would that make a difference at all? Is that the proper way of doing things?Also, some strings are used in a ton of different places and they're basically just being copied from one class and pasted into another. So, do you think I should do what I suggested above, but with a class whose sole purpose is to house those strings so that the code isn't duplicated a million times everywhere? Would that be the most efficient way of doing things?
I'm new in .NET programming.I have a class Form1 that includes Button1_Click event.Button1_Click creates a multiple Text Boxies at run time)Here is the class:
Public Class Form1 Dim shiftDown As Integer Dim counter As Integer
i am using a c++ dll to control a usb device. a while back i created a vb6 program that interfaced with the dll.it worked perfectly.now i am trying to make one in vs2008.here is the header of the function i am trying to use in teh c++ dll [code]but this get no value for textbuffer.and after the function is called a few times it gives me a memory error. i think it is because the string is not fixed length.is there a way i can get this to work in vb.net without rewriting the dll
We all know what a Static variable means! Recently I came across a problem that I have no idea about! I even don't know whether I'm wrong somewhere or that is a VS fault. Whatever it is, I can't figure out the cause. Anyway, I simply opened a VB 2008 project and added 2 Windows forms to it: Form1 and Form2. Then I set Form1 as a MdiContainer by setting its IsMdiContainer property to True. Then I added a CommandButton to Form1 and put this following code into that:
I am creating a kind of a "naive" search engine.What I have done is distributed words in files where each file corresponds to the starting letter of the words (i.e. if its English, then 26 files are there)Then when the search system loads I am loading all the words in hash tables (26 hash tables corresponding to 26 alpha-characters) for which I am using an array of structures.The problem is after declaring the variables in a Form load subroutine, the variables are not able to use those values in other subroutines..How do I properly declare them so their values persist?
One would think I'd already know this, but I never really gave it much thought before now. When declaring a member variable for a class, is it better to set the default value at the declaration
Private m_strMyVariable As String = "" Or is it better to do it in the constructor Private m_strMyVariable As String
[Code]....
Should I maybe always specify a value at declaration, even if it's Nothing, and just override that value in the constructor(s) as needed? Or is it situation specific? If so, a really quick rundown of which situations might warrant which treatment would be nice.
I have an xml document on the internet right. Lets say it contains: <tag>goose</tag> What I want to do, is when the user clicks a button in my vb form it looks for the "tag" tag and finds the text inside the tags which is goose. Then it sets a label to equal goose, or whats in those tags.
Public Class Question Private Shared _field as Integer = CrazyIntegersRepository.GetOne() ' Some other useful things go here End Class
And the method GetOne throws an exception... How can we manage that? Is a good practice to rewrite that into a static constructor? When is the GetOne method going to be executed if we leave it there in the inline _field declaration?
I try to create a sub main in a project but i can not.I have create a module called Module 1 and inside i have created a Main Sub which is intended to creta a thesaurus_form class instance , like this Code: Module module 1Public Sub Main()Dim thesaurus_form2= New Thesaurus_formEnd SubEnd module.Instead of this, once it has cretaed a first instance of the thesaurus_form class, it creates another one what i dont want at all..How can i do do make it execute the code which is inside the thesaurus_form_load sub..I also can not create a global variable or a staitc variable, because i receive this message.static is not valid in a member variable declaration.
I just recently learned about the uses of static local variables in VB.NET and wondered about it's potential use in lazy loading properties.
Consider the following example code.
Public Class Foo Implements IFoo End Class
[Code].....
As far as i can see, this has a few advantages over the usual implementation, primary your inability to access the variable outside of the property, as well as not having to use an additional variable.
My question to you is: Which of those is the "right" way to do it? I know that static variables have additional overhead, but is it bad enough to create, in my personal opinion, unclearer code that can be misused easier? How much performance do you lose compared to the "traditional" method? How does it matter for small classes compared to huge factories?
How do I declare/define a ResourceManager in the following code so it doesn't equal Nothing when it reaches rm.GetString("Magnitude") in the following code? My.Settings.. is returning a valid string.
and when I run my app, I get a SQL error that tells me that I need to declare a value for '@payperiodstartdate' but I know that that value is declared because the first query runs fine. I am told that the line where the error is is line 59, which is this line [code]...
I'm working on a home project using DirectShow.Net. to learn some VB.net. Most of the examples I've found have all been in C# so I'm looking through code for ideas and converting where I need to. I keep stumbling upon these declarations and I'm unsure how to convert it to a VB.Net statement.[code]Then the second part seems to be assigning the value but as its made up of two parts im unsure how that works?
I am writing a code for a webapplication in vb.net. I am using a shared variable in the vb code.
Consider the static variable value is 3 for a user who hits the web application. Again when another user hits the same web application, whether the static variable will be 3 again or whether he will have a separate value for static variable for his session?
wondering about the relatively efficiency of declaring oop variables in the loops, emselves, or declaring them before first use. Here are some examples:Declare early:
Dim ix As Integer Dim currentNode As System.Xml.XmlNode For ix = 1 To 100
I have noticed in VB.Net that most Dim statements also include an assignment. Eg:Dim myvar As String = "Hello World"As this wasn't possible in VB6 I have always done the following:
I have been searching the internet trying to understand in its simplist form why this behavior happens.
Dim mysingle As Single = 456.11 Dim mybool As Boolean = mysingle = 456.11
In the lines above mybool becomes false. I found this behavior when putting the single into a double I found extra digits showing. The .net documentations states a single is an approimate value I gatehr a single is a 32bit floating point number? But why are extra digits appearing when I have explicitly said what the number is.. surely the memory should store that numbers either side of my number are 0 to fill up the memory location?
I have 10 checkboxes on my screen. I have a variable setup called "case" as a string. I want to know how I can say: If checkbox1 is checked then case would be equal to "this". If checkbox2 is checked then case would = "that" Example of something I tried to cook up but didn't work because it tells me that I can't only use this in a "select case".
Dim Case as string If checkbox1.checked = true case = test1 end if If checkbox2.checked = true [Code] ......
I have the following code: Public Class TestClass Public Sub Main() If theGlobal IsNot Nothing Then Throw New Exception("What gives!") End Sub Private Shared theGlobal As Object = Nothing [Code] ..... Why is theGlobal object NOT Nothing?
which declares a temporary bucket variable and then assigns the associate property values to the variable. Which then sends it to the XMLElement AppendChild method. What is this design concept called? What is the conversion to VB.Net? I have tried using my own online utility that does a 90-95% conversion rate from C# <-> VB.Net. It has failed in this instance, and so need a hand-up on what i am looking to do to convert this from C# to VB.Net. I would really like to not have to do a long-declaration of a variable with assignments, if at all possible.