converting int to char

  • Thread starter Thread starter Nikhil Patel
  • Start date Start date
Sounds like most of this is just plain sound coding practices.
Personally, I've found most performance issues are due to implementation, and
rethinking the logic and implementation is more appropriate than trying to
squeeze in more ill-conceived operations per second.
As far as Collections go, I agree. In most cases, if a Collection is appropriate
I implement my own strongly typed collection and querying logic.
So in the end, I still don't see the point of removing the reference to the DLL.
In my case, I knew that would be the case as I use the heck out of the VB stuff,
but I was curious.

Although with the recent chatter about Strings, I may research this some more
and some changes in my usage may be beneficial.

Thanks,
Gerald
 
Hi all,
How can I convert an integer to its equivalent ascii character without
using Microsoft.VisualBasic dll or any other dll(I want to reference only
System.dll).

Thanks.

-Nikhil
Click to expand...

Dim s as string
Dim i as integer = 13

s = chr(i)

s now equals CR

HTH,
Tibby
 
I'm not sure of any performance issues - most of my stuff is utilities,
nothing overly large or processor hungry.
Obviously one less DLL in the bin folder when you're distributing apps is
useful sometimes - might even fit on a floppy if you're lucky!!
I suppose I was curious the first time to see how many imports and
references I could remove.. lol.. I can actually get most programs to not
use any VisualBasic libraries - I guess making a "pure" .NET app makes me
feel just that little bit better :)
________________________________
The Grim Reaper
 
heh, but as Jay pointed out, the VisualBasic libaries are part of the .Net
library, so you wouldn't be distributing that DLL anyway.
but writing utilities that use nothing more than the System.dll might be a fun
exercise.

Gerald
 
Back
Top