Re: CTP Hell
- From: "Willy Denoyette [MVP]" <willy.denoyette@xxxxxxxxxx>
- Date: Tue, 21 Jun 2005 11:52:31 +0200
"Michael Rodriguez" <mike@xxxxxxxxxxxxxxx> wrote in message
news:%23sHPNredFHA.3324@xxxxxxxxxxxxxxxxxxxxxxx
> "Willy Denoyette [MVP]" <willy.denoyette@xxxxxxxxxx> wrote in message
> news:eiJXdVedFHA.1384@xxxxxxxxxxxxxxxxxxxxxxx
>> It's clearly stated on the download page that they aren't compatible [1],
>> if you need both of them, run them on separate boxes.
>> If you install the VS June CTP's, you have to un-install the previous
>> versions anyway, and reinstall in the; order VS followed by SQL server,
>> this is the way it works when you are dealing with pre-beta software, and
>> this is also something you accepted when installing the bits, you did
>> read the readme files did you?.
>>
>
> Willy,
>
> I know it's clearly stated. And yet, I still reserve the right to
> complain. I do have that right, don't I?
>
> It just seems to me that the June CTPs of products that are ultimately
> meant to work together, should in fact, work together. MS clearly wants
> VS developers to use SQL Server, and vise versa, so you would think they
> would make more of an effort to make them compatible. After all, the
> builds came out within 2 weeks of each other.
>
> Mike
>
>
>
You have the right to complain, just like I reserve the right to say you
shouldn't complain, and you shouldn't start your rant with "who is the
genius", instead you should be wondering 'Is this release for me?'.
First off, it's clearly documented what you can/can't expect from a CTP
build:
- SQL June TCP/VS June CTP is not supported on the same box (CLR issue), if
you did waste your time trying to install both, you only have to blame
yourself
- both are unsupported and not of Beta quality, if you aren't willing to
deal with and accept the issues (something you clearly don't), don't
install.
- It's not for production code using Beta2 Go-live license, if this is what
you need, stick with Beta2.
- Unless you have plenty of hardware or you are using VPC's, just don't
install it.
If however, you have the hardware and ready to accept the issues and you
really need to use the SQL June CTP with VS, install them on a separate box
and point your VS June CTP Dataconnections to this remote instance, that's
the way I'm doing , sure there are issues, but it works pretty well,
considering both aren't even Beta quality.
Second you should keep in mind that while SQL 2005 integrates into VS (to a
certain extent), they are totally different products, built by different
teams, targeting different customers/needs.
IMO it was the correct decision to separate both product development cycles,
and don't let them depend on each other. SQL Server does not need VS, and VS
doesn't require SQL in order to build applications. Right, both products
have the CLR in common, but he! SQL server doesn't need the CLR to run (most
of the SQL community doesn't care at all about the CLR), while VS needs it
badly. As indicated by others, it wouldn't be acceptable to delay the
release of one of the product in favor of the other, just because someone
needs synchronized pre-beta builds.
Willy.
.
- References:
- CTP Hell
- From: Michael Rodriguez
- Re: CTP Hell
- From: Willy Denoyette [MVP]
- Re: CTP Hell
- From: Michael Rodriguez
- CTP Hell
- Prev by Date: algorithm question
- Next by Date: Re: hiding vs. overriding
- Previous by thread: Re: CTP Hell
- Next by thread: design-time-only references
- Index(es):
Relevant Pages
|
