I'm not sure Microsoft would know if you moved your applications to the RC
if you have them internal, but to distribute them to customers is the issue.
It may because this version is only available to MSDN subscribers, and the
beta 2 was public.
I went ahead and moved my internal stuff to the RC, and I am glad I did.
The database schema for the security provider is different between Beta 2 and
the RC (and presumably the RTM), and this was not mentioned in the difference
documentation! For a desktop application there werer differences in some of
the forms and report objects as well that were not listed.
Even if you can't deploy (my ISP only supports Beta 2), you should go
through the upgrade process as soon as possible.
[quoted text, click to view] "Bob Chauvin ( Paix dehors )" wrote:
> FWIW, I agree.
>
> Why not allow us to deploy with the best current tool? Must be the
> marketing folks had something to say.
> --
>
> VS2005B2, VSTO 2005B2
> "John Bailey" <JohnBailey@discussions.microsoft.com> wrote in message
> news:61C03732-2346-44CB-A254-00EB8909C05C@microsoft.com...
> > Okay, so I am very excited to see the release candidate released. I have
> > two
> > projects in the works under the Go-Live license, and I am hoping that the
> > release candidate will be a more stable environment while I am finishing
> > these up for my clients.
> >
> > That is until I hear that the release candidate is not covered by the Beta
> > 2
> > Go-Live license and there apparently is no Go-Live license for it
> > separately.
> > Since it is more stable that Beta 2, why would there not be a Go-Live
> > license for it? Both of these should finish up around the first week of
> > October, and I would really like to complete them on the more stable
> > version.
> >
> > Even if Microsoft doesn't want to extend the Beta 2 Go-Live to cover it, I
> > wish they would allow another agreeemnt.
> >
>
>
