Re: Just Curious

You are very right. I forgot we are in a marooned ship called VB6. Thanks
for reminding me.

"Veign" <NOSPAMinveign@xxxxxxxxx> wrote in message
news:e7iM9hvWFHA.3676@xxxxxxxxxxxxxxxxxxxxxxx
> Don't expect any changes to the MSDN when it comes to VB6 - at least
> samples.
>
> --
> Chris Hanscom - Microsoft MVP (VB)
> Veign's Resource Center
> http://www.veign.com/vrc_main.asp
> --
> Read. Decide. Sign the petition to Microsoft.
> http://classicvb.org/petition/
>
>
> "JoeO" <jp3bless_NoSpam@xxxxxxxxxxx> wrote in message
> news:%23ZsTAfvWFHA.3760@xxxxxxxxxxxxxxxxxxxxxxx
> > LOL
> > Problem actually is lack of detail document of controls and help topics.
I
> > think I will feel better when MSDN corrects that.
> >
> >
> > "Veign" <NOSPAMinveign@xxxxxxxxx> wrote in message
> > news:%2362CUZvWFHA.3760@xxxxxxxxxxxxxxxxxxxxxxx
> > > feel better now?
> > >
> > > --
> > > Chris Hanscom - Microsoft MVP (VB)
> > > Veign's Resource Center
> > > http://www.veign.com/vrc_main.asp
> > > --
> > > Read. Decide. Sign the petition to Microsoft.
> > > http://classicvb.org/petition/
> > >
> > >
> > > "JoeO" <jp3bless_NoSpam@xxxxxxxxxxx> wrote in message
> > > news:%23kfAlSvWFHA.1240@xxxxxxxxxxxxxxxxxxxxxxx
> > > > I would like know... are the folks at MSDN professional programmers
> who
> > > thus
> > > > know how to organize, explain and present MSDN library topics in
> useful
> > > easy
> > > > to find and understand format or are they just technical writers who
> do
> > > not
> > > > understand the real programming world and thus can't crank "who
cares
> > > what"
> > > > detail. Why is MSDN so full of "Hello World" kind of samples and
less
> of
> > > the
> > > > type real programmers really need to understand the topic.
Ahhhhhh...
> I
> > > know
> > > > it... it's me after all.
> > > >
> > > >
> > >
> > >
> >
> >
>
>


.

Relevant Pages

  • Re: Please do NOT sign the VB.COM petition
    ... I think that the proposed solution is one of the cheapest possible solutions which will please the VB6 community. ... I know some dozens of people who signed the petition, and only /very few/ of them believe the suggested way is the only way. ... However, I don't think this is a good idea, because it costs Microsoft money without bringing money back to Microsoft. ... All of those other teams are taking lots of resources from the .NET Framework and VB.NET teams. ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Microsoft not content with "dissing" just the Classic VB Developer Army....
    ... I've read the petition and I can't ... Microsoft can satisfy the "issues" in the petition (which pretty much boil ... Nothing but adding unmanaged VB6 into the VS.NET IDE ... COM interop support, a poor code conversion wizard, the ending of mainstream ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Please do NOT sign the VB.COM petition
    ... However, I don't think this is a good idea, because it costs Microsoft money without bringing money back to Microsoft. ... But instead of Microsoft creating and selling VB.COM being seen as the company answering the requests of the VB6 community, I personally believe that it would be seen as a blatant money-grab. ... petition doesn't /request an SP7/, it /suggests to create a new version/. ... Tons of whitepapers don't really help because they won't take the work away from people "upgrading to" (more appropriately: "rewriting in the new programming language") VB.NET. ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Please do NOT sign the VB.COM petition
    ... >> the context of a petition is something more than a suggestion. ... petition's request that Microsoft create VB.COM, ... >>> version of VB6, VB.COM for example, would bring money back which can be ... >>> If the code upgrade wizard could be improved to a stage where it is ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Please do NOT sign the VB.COM petition
    ... >>> is one of the cheapest possible solutions which will please the VB6 ... not a request (see petition FAQ). ... > Microsoft money without bringing money back to Microsoft. ...
    (microsoft.public.dotnet.languages.vb)
Loading