Re: Creating a self deleting executable using .NET

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Bill,

Try to see it this way, I know this is difficult for you.

You write Australian English, some write American English, some write classic English and I write Giblish English.

And we all think that ours is the real one.

The same is with VB.

If those we have this discussion now would speak more languages, then the would be able to see that the differences in VB are less than the differences in English. (Beside mine of course)

Cor


"Bill McCarthy" <bill@xxxxxxxxxxxxx> wrote in message news:OiumNRxbKHA.5156@xxxxxxxxxxxxxxxxxxxxxxx
Hi Henning,

"Henning" <computer_hero@xxxxxxxxxxxx> wrote in message news:uAagufwbKHA.1652@xxxxxxxxxxxxxxxxxxxxxxx
Hi Bill,

"Bill McCarthy" <bill@xxxxxxxxxxxxx> skrev i meddelandet news:%23Jgxsd9aKHA.5472@xxxxxxxxxxxxxxxxxxxxxxx
Hi David,

"David Kaye" <sfdavidkaye2@xxxxxxxxx> wrote in message news:heclbe$aqg$2@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
This newsgroup is for VB6 and its lineal predecessors, and always has been.

This newsgroup is vb.general.discussion. It was not designed specifically for VB6: if it was it would have VB6 in the name. There are specific newsgroups for .NET just as there are for win API, graphics etc, and where appropriate questions on specific areas should be redirected *WITHOUT* all the childish name calling and other nonsense. In this particular case the question does not necessitate a specific .NET solution.


It *was* created for VBx long before the new .nxt version was even in anyones mind.

Huh ? VBX is the name sometimes given to VB10, the X being the roman symbol for 10. I guess you meant to write VBn where n is some number. In that case you are correct, and it certainly does not end at 6 ;)

Since .nxt has got its very own groups, why can't this group be left alone for the older versions? The reason Microsoft started the new groups must have been because the confusion mixed posts is creating.


Again I really don't think you get it. Please read again my post you replied to. This newsgroup pre-dates VB6 and is NOT VB6 specific.
It is as the name suggests, VB.general.discussion. Just as there are specific newsgroups for winapi, eg vb.winapi, there are also ones specific for dotnet, eg dotnet.languages.vb. The right thing to do is redirect as needed in both cases. But we don't see a bunch of anti winapi zealots in here jumping on any post that includes winapi, we do however see a handful jump on .NET related posts as if it was the end of the world. It is those anti .NET people that make all the fuss, make this thread over 100 posts instead of just three and in doing so promote this newsgroup in any search on .NET. It is those people who would like the world to think there is no common ground between the versions of VB, whilst other folks will tell you there is. It is those people who are rude, use foul childish gutter slang etc, etc, etc.

Really I think you need sit back, relax, and stop making mountains out of mole hills. These newsgroups are to help other developers. If you don't like .NET so be it, but all this wasted bandwidth and rhetoric whenever it is mentioned in here does nothing **CONSTRUCTIVE** for anyone. Sadly I still doubt you'll listen to what has been said; instead you'll probably post back insisting you are right and continue making this a mess for everyone. Ask yourself who are you really helping ?

Oh, please don't expect any further replies to this thread from me. Seriously this has been discussed in the past ad nauseum; and it is these childish bickering threads that ensue that are the real problem, not the original post or the offers of help.






The problem is that NET is not VB6. I'm an expert on VB6 but know little
about NET. I can write bug-free code for file manipulation, voice
recognition, SQL, whatever, while half awake and it will work exactly as
intended the first time around. With VB-NET I'd have to have manual pages
open and struggle to get through code line by line.


Well that's very sad as I personally found the transition to VB7 and later quite easy, and I am amazed you find that stuff difficult so many years later. A real problem I see is often advice on coding in VB6 fails to take into account prior art and moving one's code forward to VB7 or later

/Henning


.

Relevant Pages

  • RE: Google in English
    ... English and you get www.google.com. ... Explorer to access a redirected Web page and Internet Explorer uses ISA ... This newsgroup only focuses on SBS technical issues. ... you may want to contact Microsoft CSS directly. ...
    (microsoft.public.windows.server.sbs)
  • Re: PHPMailer-FE und IIS
    ... Which does not mean it is not an English language newsgroup. ... Sorry you're having trouble grasping that. ...
    (comp.lang.php)
  • Re: IrCOMM Socket options
    ... The main reason why i posted this question in this particular NewsGroup was ... communications link to embedded devices, since the .NET IrDA Classes lack ... To the point "german newsgroup": I am simply used to write in english no ...
    (microsoft.public.de.german.entwickler.dotnet.csharp)
  • Re: PHPMailer-FE und IIS
    ... Auf meiner Homepage funktioniert zumindest ein Beispiel aber für Entwicklungszwecke auf meinem lokalen IIS 7.0 Server bekomme ich nur ... This is an English language newsgroup; ... there are many German-speaking newsgroups - but I don't go posting English questions in those. ... The world is not how YOU would like it. ...
    (comp.lang.php)
  • Re: Message =?iso-8859-1?Q?inexpliqu=E9?=
    ... not restricted to English. ... this IS the international newsgroup! ... international officialese is English not German or French. ... Internet, then French it is also in this newsgroup. ...
    (comp.lang.pascal.delphi.misc)