EpiServer 7.1 - Patch 3 no longer available?

steve@vividgroup.com.au

Vote:

Would appreciate some help with the following migration issue:

To migrate a CMS 6R2 Composer reliant site to CMS 7.1, Patch 3 is required according to Episerver Migration page:

EPiServer 7 CMS/7.1 Patch 3 - the target solution should be set up with CMS version 7.1 with Patch 3. If you want to use a later version, you can upgrade your CMS after the migration has been completed.

Migration advise here:http://world.episerver.com/documentation/Items/Installation-Instructions/EPiServer-Composer/Migrating-Composer-websites-to-CMS-7/

However, it appears Patch 3 is no longer available, unless I'm missing something?

https://nuget.episerver.com/en/OtherPages/Package/?packageId=EPiServer.CMS.Core&packageVersion=7.0.586.16

Running a package request in Visual Studio 12 returns the following error:

PM> Install-Package EPiServer.CMS.Core -Version 7.0.586.16
Install-Package : Unable to find version '7.0.586.16' of package 'EPiServer.CMS.Core'.
At line:1 char:16
+ Install-Package <><><>< episerver.cms.core -version 7.0.586.16>

Does anyone have any idea if Patch 3 is still available please?

Cheers

Steve

#114873

Dec 27, 2014 6:16

Vote:

What is your project's target framework? I recon it could be 4 as it is an EPi6 site. I ran into a similar issue before upgrading NuGet packages to versions targeted on 4.5, the update went through once I changed my target framwork to suit the package.

//Mathias

#114874

Dec 27, 2014 18:40

steve@vividgroup.com.au

Vote:

Thanks Mathias, think my method of creating a clean CMS 7 MVC web Site is the issue.

I tried Deployment Centre, but clean sites generated this way do not appear to have any VStudio project files created as part of the process.

Whereas using the latest Visual Studio 2012 Extension to create an empty MVC CMS web site seems to provide no option to select CMS 7 rather than CMS 7.5 assemblies as project references.

The link below mentions support for both 7.0/7.5 CMS projects in history of prev. release notes but no indication of how to select 7.0 in current version:

http://world.episerver.com/blogs/Per-Bjurstrom/Archive/2014/5/New-version-of-Visual-Studio-extension-available/.

Once I have a new empty CMS 7.0 MVC Site with VStudio support then running the Package Manager Console should work to upgrade to Patch 3.

Really didn't think creating an empty CMS 7 MVC Site with VStudio 2012 support would prove to be so difficult, maybe I'm missing some documentation?

Cheers

Steve

#114875

Dec 28, 2014 4:07

Shahid nawaz

Vote:

Hi Steve,

I just upgraded my EPiServer 7 site to Patch-3 through Package Manager Console by running: PM> Install-Package EPiServer.CMS.Core -Version 7.0.586.16

Just to double check that you have pointed to correct episerver nuget feed in VS i.e. ?

Go to Settings for NuGet package manager in Visual Studio and add "http://nuget.episerver.com/feed/packages.svc/".

#114882

Dec 29, 2014 9:16

steve@vividgroup.com.au

Vote:

Hi Shahid,

Thanks for confirming my initial problem and your suggestion works perfectly.

However, my real problem is creating a Visual Studio Solution for a CMS 7 web site .

(I can run Install-Package EPiServer.CMS.Core -Version 7.0.586.16 from within the solution generated by VS Episerver Extension for CMS 7.5)

But I haven't seen a way of automatically generating an empty web site solution for Episerver CMS 7.0 on VS2012.

i.e a VS2012 project that references 7.0.*.* assemblies, has a pre-configured web.config/episerver.config and wired-up MVC support.

The latest VS Extension provides an empty Episerver MVC site which works fine, but for CMS 7.5.

More difficult than I thought to get up and running....

Cheers

Steve

#114891

Dec 30, 2014 10:05