Why I am sick of .Net

[aalbino]

If your gonna flame, shut up and read first:

I have been programming in VB (5, 6), VB.NET (1.0,1.1, 2.0), VBA, etc..
since 2000.

I really loved working with that RAD tool, Visual BASIC IDE, and Visual
Studio .Net.

But the think that just drives me past the brink of flipping insanity
is the FACT that half the crap thats supposed to work a certain way in
VB6 or .NET just plain DOESN'T!!!!!!!

WHAT THE @*&!# HECK!!!!

Always with the stupid 'workaround' solutions. Burn VB!, burn to a
crisp. I hope you die of a lethal flatite. Everyone hates you VB,
Nobody likes you. I certainly dont. And I hope you and your stupid
'workaround' functionality all just explodes into a gazillion snippets
of code. So there!
Well, enough of that. Hope you all enjoyed my dumb post. :-)

[Cor Ligthert [MVP]]

Aalbino,

I would not say it your way, however I agree with you that it seems that
Microsoft is more and more busy hunting the next never to use solution, than
making the ones that have proven themselves to be needed really working for
100% correct.

Just my opinion.

Cor

<aa*****@comcas t.netschreef in bericht
news:11******** **************@ 80g2000cwy.goog legroups.com...

If your gonna flame, shut up and read first:

I have been programming in VB (5, 6), VB.NET (1.0,1.1, 2.0), VBA, etc..
since 2000.

I really loved working with that RAD tool, Visual BASIC IDE, and Visual
Studio .Net.

But the think that just drives me past the brink of flipping insanity
is the FACT that half the crap thats supposed to work a certain way in
VB6 or .NET just plain DOESN'T!!!!!!!

WHAT THE @*&!# HECK!!!!

Always with the stupid 'workaround' solutions. Burn VB!, burn to a
crisp. I hope you die of a lethal flatite. Everyone hates you VB,
Nobody likes you. I certainly dont. And I hope you and your stupid
'workaround' functionality all just explodes into a gazillion snippets
of code. So there!
Well, enough of that. Hope you all enjoyed my dumb post. :-)

[Spam Catcher]

aa*****@comcast .net wrote in news:1165639966 .164986.220650@
80g2000cwy.goog legroups.com:

But the think that just drives me past the brink of flipping insanity
is the FACT that half the crap thats supposed to work a certain way in
VB6 or .NET just plain DOESN'T!!!!!!!

What 1/2 doesn't work?

[Henry Jones]

I think he has it installed on his Radio Shack TRS-80.

That could be the problem!
"Spam Catcher" <sp**********@r ogers.comwrote in message
news:Xn******** *************** **********@127. 0.0.1...

aa*****@comcast .net wrote in news:1165639966 .164986.220650@
80g2000cwy.goog legroups.com:

>But the think that just drives me past the brink of flipping insanity
is the FACT that half the crap thats supposed to work a certain way in
VB6 or .NET just plain DOESN'T!!!!!!!

What 1/2 doesn't work?

[aalbino]

Henry Jones wrote:

I think he has it installed on his Radio Shack TRS-80.

That could be the problem!
"Spam Catcher" <sp**********@r ogers.comwrote in message
news:Xn******** *************** **********@127. 0.0.1...

aa*****@comcast .net wrote in news:1165639966 .164986.220650@
80g2000cwy.goog legroups.com:

But the think that just drives me past the brink of flipping insanity
is the FACT that half the crap thats supposed to work a certain way in
VB6 or .NET just plain DOESN'T!!!!!!!

What 1/2 doesn't work?

@Henry Jones: Its all about the 5 1/4 floppy. :-)

Here is what doesnt work:

-Memory related api in Managed Direct X
-Working with memory bitmap bits in GDI+ (again, mostly memory
manipulating related)
-Methods that are supposed to work one way, but dont. (It turns out a
certain method or function is deprecated in version X.x.x of the
framework)

BTW: My machine is nice and new, not old or junky. Thanks.

[Oenone]

aa*****@comcast .net wrote:

But the think that just drives me past the brink of flipping insanity
is the FACT that half the crap thats supposed to work a certain way in
VB6 or .NET just plain DOESN'T!!!!!!!

For example?

I've been programming for a lot longer than the last six years, using lots
of languages including VB back to version 3, C/C++, and a variety of
assembly languages (the good ol' days :-). And against all that, I think VB
(VB6 and VB.NET) are both pretty damn good.

In my experience complaints like this are usually from people who
misunderstood how it was supposed to work in the first place.

So let's see a few good examples of the crap that doesn't work, please. I
assume you're just trolling but you can prove me wrong if you like.

--

(O)enone

[Cor Ligthert [MVP]]

Henry,

>I think he has it installed on his Radio Shack TRS-80.

That could be the problem!

Aalbino is telling in his way his problem with Microsoft products, although
he tells in the same way that he is a fervent user of it.

I don't think that your reaction is accoording his message.

Just my thought,

Cor

[aalbino]

I certainly can. Try handling bitmap bits directly in VB.NET (1.0, 1.1,
maybe even 2.0)
You cant. Not without breaking managed code and using DLL hell.

C# can do it, and only because it can be forced to use unmanaged C++
within code.

If you need more, go to google.com, and search form "vb workaround".

So there. Your wrong. ;)

Oenone wrote:

aa*****@comcast .net wrote:

But the think that just drives me past the brink of flipping insanity
is the FACT that half the crap thats supposed to work a certain way in
VB6 or .NET just plain DOESN'T!!!!!!!

For example?

I've been programming for a lot longer than the last six years, using lots
of languages including VB back to version 3, C/C++, and a variety of
assembly languages (the good ol' days :-). And against all that, I think VB
(VB6 and VB.NET) are both pretty damn good.

In my experience complaints like this are usually from people who
misunderstood how it was supposed to work in the first place.

So let's see a few good examples of the crap that doesn't work, please. I
assume you're just trolling but you can prove me wrong if you like.

--

(O)enone

[Mudhead]

>I certainly can. Try handling bitmap bits directly in VB.NET (1.0, 1.1,

maybe even 2.0)
You cant. Not without breaking managed code and using DLL hell.

Huh?

Dim bmData As New BitmapData()

bmData = bm.LockBits(New Rectangle(0, 0, bm.Width, bm.Height),
ImageLockMode.R eadWrite, PixelFormat.For mat32bppRgb)

Dim stride As Integer = bmData.Stride
Dim scan0 As IntPtr = bmData.Scan0

Dim bits(bm.Height * stride - 1) As Byte

Marshal.Copy(sc an0, bits, 0, bits.Length)
<aa*****@comcas t.netwrote in message
news:11******** **************@ l12g2000cwl.goo glegroups.com.. .

>I certainly can. Try handling bitmap bits directly in VB.NET (1.0, 1.1,
maybe even 2.0)
You cant. Not without breaking managed code and using DLL hell.

C# can do it, and only because it can be forced to use unmanaged C++
within code.

If you need more, go to google.com, and search form "vb workaround".

So there. Your wrong. ;)

Oenone wrote:

>aa*****@comcast .net wrote:

But the think that just drives me past the brink of flipping insanity
is the FACT that half the crap thats supposed to work a certain way in
VB6 or .NET just plain DOESN'T!!!!!!!

For example?

I've been programming for a lot longer than the last six years, using
lots
of languages including VB back to version 3, C/C++, and a variety of
assembly languages (the good ol' days :-). And against all that, I think
VB
(VB6 and VB.NET) are both pretty damn good.

In my experience complaints like this are usually from people who
misunderstoo d how it was supposed to work in the first place.

So let's see a few good examples of the crap that doesn't work, please. I
assume you're just trolling but you can prove me wrong if you like.

--

(O)enone

[aaron.kempf]

ful;ly agree Cor; I think that MS needs to stop selling new versions
and start fixing bugs

I hope that was a good paraphrasing.

And I think that you deserve a FRIGGIN MEDAL DUDE.

Well spoken; thank you for your time, Cor

-Aaron
Cor Ligthert [MVP] wrote:

Aalbino,

I would not say it your way, however I agree with you that it seems that
Microsoft is more and more busy hunting the next never to use solution, than
making the ones that have proven themselves to be needed really working for
100% correct.

Just my opinion.

Cor

<aa*****@comcas t.netschreef in bericht
news:11******** **************@ 80g2000cwy.goog legroups.com...

If your gonna flame, shut up and read first:

I have been programming in VB (5, 6), VB.NET (1.0,1.1, 2.0), VBA, etc..
since 2000.

I really loved working with that RAD tool, Visual BASIC IDE, and Visual
Studio .Net.

But the think that just drives me past the brink of flipping insanity
is the FACT that half the crap thats supposed to work a certain way in
VB6 or .NET just plain DOESN'T!!!!!!!

WHAT THE @*&!# HECK!!!!

Always with the stupid 'workaround' solutions. Burn VB!, burn to a
crisp. I hope you die of a lethal flatite. Everyone hates you VB,
Nobody likes you. I certainly dont. And I hope you and your stupid
'workaround' functionality all just explodes into a gazillion snippets
of code. So there!
Well, enough of that. Hope you all enjoyed my dumb post. :-)