Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / Visual Studio.NET / General / July 2007

Tip: Looking for answers? Try searching our database.

VS beta 2 and its relation with other products

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
waltera - 30 Jul 2007 18:22 GMT
I want to install VS beta 2 pro on my Vista Ultimate PC, and to have it work
with a Windows 2003 Server on another PC. I wanted to try both SharePoint
Designer 2007 and the Expression Suite. Reading through the various
documents, I come across some ambiguities that I would like to have cleared
up before starting.  On my Vista I have .Net 1.1 and also .Net 1.0 running,
and even VS 2002. I need those for various reasons.

The installation readMe for VS beta 2 states :
2.1.1 : "If you have installed an earlier version of Visual Studio, such as
a Visual Studio Code Name "Orcas" Community Technical Preview (CTP), then you
must uninstall it in the following order...". Since this does not explicitly
restrict to which earlier version of VS the uninstall "must"be done, it is
not clear whether this VS beta 2 really can coexist with other VS versions.
It is not clear whether the uninstall "must" be done for a previous beta
only, and not for other, non beta VS versions.

2.1.7 : "Installing Visual Studio 2008 on the same computer as Visual Studio
2005 causes Visual Studio 2005 repair of .NET Framework 2.0 to fail". This
makes me worry  about what to expect if prior versions of VS (prior to VS
2005) are installed on the same computer.

2.1.15 : "Visual Studio SharePoint Workflow features have specific
installation requirements...  To use the SharePoint workflow tools in this
release, you must install the following products and components in the
specific order listed ... Windows 2003 Server ... .NET Framework 2.0 & 3.0
... Microsoft Office SharePoint Server 2007 ... ". Confusing. Does this mean
that in order to use VS SharePoint Workflow features I need to install VS
beta on a Server 2003, instead of using as a server my other PC running
Server 2003 ? I am not really familiar with SharePoint (Designer or
Services), installing the trial versions was meant to make me familiar with
these new products, so I need to have this cleared up before I start
installing the lot. And why do they state ".NET Framework 2.0" as an explicit
requirement ?

2.2 "Uninstalling ... 2.2.1 On machines with previous versions of Visual
Studio...", where they discuss the implications for VS 2005 and later, but
there is no mention of the uninstall impact to previous versions of VS,
before VS 2005. VS 2005 would have "some of its features stop working", but
what with the previous versions ? And maybe a hint of which features might be
affected would give an idea of the impact ?

As for the installation readMe of FrameWork 3.5 beta 2 :
2.3.1.6 "Microsoft Blend will check for a specific earlier version of
Windows Presentation Foundation during installation and then fail...". Does
this mean that Blend will not work at all with VS beta 2 ? (another remark
about this statement : knowing the subtle change of product names occurring
so often, this statement had me also confused because of use of the name
"Microsoft Blend" instead of "Expression Blend")

Another remark of general confusion :
when will they learn to put at least one date in all of those documents, at
least the creation date if not the last update date (supposing that they will
update the documents instead of having them around with outdated
information).
David Wilkinson - 30 Jul 2007 18:49 GMT
> I want to install VS beta 2 pro on my Vista Ultimate PC, and to have it work
> with a Windows 2003 Server on another PC. I wanted to try both SharePoint
[quoted text clipped - 50 lines]
> update the documents instead of having them around with outdated
> information).

waltera:

I don't know the answer to any of your questions, but have you thought
of trying the VPC version of Orcas Beta 2? That's what i did (and with
Beta 1 also). No problems so far.

Signature

David Wilkinson
Visual C++ MVP

waltera - 30 Jul 2007 19:10 GMT
Yes, I had it downloaded already, but have not installed it yet as I do not
clearly understand the implications. I guess it would insulate me from
potential problems with the other VS versions, but I was afraid that it would
insulate me too much from my daily routine... Wouldn't it ? And even then,
that would not answer the other questions about the relation between VS 2008
beta 2 and both other (non VS) products as well as the server 2003 PC.
David Wilkinson - 30 Jul 2007 19:31 GMT
> Yes, I had it downloaded already, but have not installed it yet as I do not
> clearly understand the implications. I guess it would insulate me from
> potential problems with the other VS versions, but I was afraid that it would
> insulate me too much from my daily routine... Wouldn't it ? And even then,
> that would not answer the other questions about the relation between VS 2008
> beta 2 and both other (non VS) products as well as the server 2003 PC.

waltera:

The VPC version of Visual Studio comes with Server 2003 as its OS, and
this OS is running inside Virtual PC. It can just act as another machine
on your network.

There's no harm in trying it. You can just delete the files if you don't
like it. Downloading the thing is the most time-consuming part, but you
say you've done that already.

Signature

David Wilkinson
Visual C++ MVP

waltera - 30 Jul 2007 23:56 GMT
> The VPC version of Visual Studio comes with Server 2003 as its OS, and
> this OS is running inside Virtual PC. It can just act as another machine
[quoted text clipped - 3 lines]
> like it. Downloading the thing is the most time-consuming part, but you
> say you've done that already.

Maybe I'll give it a go, but I do not need the "Team Suite" version anyway,
so I thought to stay as close as possible to my final environment when
setting up a try. In particular, I wanted to see how the various products
(VS, Expression and/or SharePoint Designer, SilverLight) cooperate when I
publish to my real server from my Vista... That is something you cannot set
up with VPC, right ? What I am trying to anticipate is which surprises are
waiting out there ;)
David Wilkinson - 31 Jul 2007 04:07 GMT
> Maybe I'll give it a go, but I do not need the "Team Suite" version anyway,
> so I thought to stay as close as possible to my final environment when
[quoted text clipped - 3 lines]
> up with VPC, right ? What I am trying to anticipate is which surprises are
> waiting out there ;)

waltaera:

You should be able to install any additional software inside the virtual
machine (licensing permitting).

Signature

David Wilkinson
Visual C++ MVP


Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.