Prev: MailMessage message size
Next: How to build the form with details button?
From: Phill W. on 24 May 2010 07:57
On 22/05/2010 21:31, J.B. Moreno wrote:

> In article<uZihjcr4KHA.6104(a)TK2MSFTNGP05.phx.gbl>,
> Cor Ligthert[MVP]<Notmyfirstname(a)planet.nl> wrote:
>
> -snip cannot use both 4.0 and Microsoft.VisualBasic.Compatibility.VB6-
> -snip yes you can, just obsolete now-

Which, of course, implies that in a future release - /any/ future
release - they could be removed.

Regards,
Phill W.
From: J.B. Moreno on 24 May 2010 23:52
In article <htdpj7$kk6$1(a)south.jnrs.ja.net>,
Phill W. <p-.-a-.-w-a-r-d-@-o-p-e-n-.-a-c-.-u-k> wrote:

> On 22/05/2010 21:31, J.B. Moreno wrote:
>
> > In article<uZihjcr4KHA.6104(a)TK2MSFTNGP05.phx.gbl>,
> > Cor Ligthert[MVP]<Notmyfirstname(a)planet.nl> wrote:
> >
> > -snip cannot use both 4.0 and Microsoft.VisualBasic.Compatibility.VB6-
> > -snip yes you can, just obsolete now-
>
> Which, of course, implies that in a future release - /any/ future
> release - they could be removed.

Yep -- in THAT release. And they *might* do that in 2012 or whenever
the next major release is (I doubt they'll do it for a minor release).

Thinking about it, I'd guess that the reason for marking things
obsolete has something to do with ADODC, and wanting to support 64bit
systems better. I'd guess that they won't be dropped until there's a
64 bit version of Visual Studio. Which I wouldn't bet on happening
anytime soon.

--
J.B. Moreno
From: Phill W. on 25 May 2010 07:41
On 25/05/2010 04:52, J.B. Moreno wrote:
> In article<htdpj7$kk6$1(a)south.jnrs.ja.net>,
> Phill W.<p-.-a-.-w-a-r-d-@-o-p-e-n-.-a-c-.-u-k> wrote:
>
>> On 22/05/2010 21:31, J.B. Moreno wrote:
>>
>>> In article<uZihjcr4KHA.6104(a)TK2MSFTNGP05.phx.gbl>,
>>> Cor Ligthert[MVP]<Notmyfirstname(a)planet.nl> wrote:
>>>
>>> -snip cannot use both 4.0 and Microsoft.VisualBasic.Compatibility.VB6-
>>> -snip yes you can, just obsolete now-
>>
>> Which, of course, implies that in a future release - /any/ future
>> release - they could be removed.
>
> Yep -- in THAT release. And they *might* do that in 2012 or whenever
> the next major release is (I doubt they'll do it for a minor release).

I don't think anyone [then] would have bet on a Service Pack for MS
Office rendering [millions of] MS Word documents unreadable, but that
didn't stop our Friends in Redmond ... :-)
http://support.microsoft.com/kb/938810

Regards,
Phill W.
From: J.B. Moreno on 29 May 2010 15:50
Phill W. <p-.-a-.-w-a-r-d-@-o-p-e-n-.-a-c-.-u-k> wrote:

> On 25/05/2010 04:52, J.B. Moreno wrote:
> > Phill W.<p-.-a-.-w-a-r-d-@-o-p-e-n-.-a-c-.-u-k> wrote:

> >>> -snip cannot use both 4.0 and Microsoft.VisualBasic.Compatibility.VB6-
> >>> -snip yes you can, just obsolete now-
> >>
> >> Which, of course, implies that in a future release - /any/ future
> >> release - they could be removed.
> >
> > Yep -- in THAT release. And they *might* do that in 2012 or whenever
> > the next major release is (I doubt they'll do it for a minor release).
>
> I don't think anyone [then] would have bet on a Service Pack for MS
> Office rendering [millions of] MS Word documents unreadable, but that
> didn't stop our Friends in Redmond ... :-)
> http://support.microsoft.com/kb/938810

There's a big difference between file types that are a security risk,
and obsolete code.

(Not sure whether or not dropping back a version of the framework
should be considered the equivalent of changing a registry setting in
order to re-enable the file types).

Anyway, yeah it's possible they could do so in a minor framework
release, but I'd bet against it.

Although, frankly, I'm at a bit of a loss as to why they'd even bother
marking them obsolete.

The only people that have much of a choice in using it are the
migration tools. They aren't providing a migration tool themselves now
and the independent tools that do migration aren't going to change just
because it's marked obsolete. They are going to use it where it seems
best and provide something else where /that/ seems best (forex it looks
like VB Migration Partner isn't going to use ADODB much longer and
that's what I see as the most significant portion of the compatibility
namespace).

Most developers are simply going to let it be and ignore it, not start
rewriting their migrated code just to get rid of a warning.

--
J.B. Moreno
First  |  Prev  | 
Pages: 1 2 3
Prev: MailMessage message size
Next: How to build the form with details button?