Publishing Umbraco with Umazel using Visual Studio was quite the challenge.
I had a long day yesterday and thought I'd share the end result. You can be up and running in a few minutes if you know what you're doing but I had a lot to learn. There didn't seem to be any complete documentation on this process so I learnt a lot by trial and error. There were lots of errors that required research, many wipe the slate and start overs and several separate test installations with and without Visual Studio to compare end results. This is a summary.
There is no guarantee there won't be more bugs related to the EnablePropertyValueConverters issue but this will at least give you a mostly operational version of Umbraco with Umazel to play with.
Visual Studio 2017 Community : Umbraco 7.10.3 : Umazel 1.0.5
Create a new project in Visual Studio. Visual C# | Web | ASP.NET Web
Application (.Net Framework 4.5)
Select Empty project and leave all the options unchecked
Right click the project and select Manage Nuget Packages...
Under Browse, search for "UmbracoCMS" and install it.
Run the project using IIS Express
It's OK to modify the web.config to enable debugging. You should
setup transforms before going live anyway.
In SQL Server Management Studio, create a new empty database and
add a user with db_owner membership.
Back in Umbraco, enter your name, email and password, tick the box
to stay updated and click customize.
You'll receive a welcome email from Umbraco with a link to a collection of short videos on document types. You should watch them before playing with Umbraco. It's not super intuitive so the videos will save you time in the long run.
Enter the database details and Continue
Continue with the default machine key.
No thanks, I do not want to install a starter website
You should be presented with the Umbraco CMS backend
Select Developer from the left | Packages | Starter kits | Umazel |
Install package | Finish
Close the browser, stop the debug session.
In Visual Studio Solution Explorer, turn on Show all files. (Icon
up the top)
Open Views | Partial | SectionText.cshtml
Change this line of code to avoid the invalid cast error caused by the
EnablePropertyValueConverters issue
switch ((int)currSection.TitleSize)
to
switch (Convert.ToInt32(currSection.TitleSize))
Select the project and run it again using IIS Express.
You should see the default front end with the "OK, now what?" header.
Close the browser and stop the debug session.
Back in Visual Studio Solution Explorer with Show All Files still enabled, right click the following folders and files and select "Include in project". Visual Studio seems to magically publish both Umbraco folders without them being included. It knows about Umbraco but not Umazel.
"bin\DotSee.AutoNode.dll"
"bin\DotSee.Common.dll"
"bin\DotSee.NodeRestrict.dll"
"bin\DotSee.PageMetas.dll"
"bin\DotSee.VirtualNodes.dll"
"bin\MailChimp.Net.V3.dll"
"bin\Umbraco.Web.PublishedContentModels.dll"
"Config\autoNode.config"
"Config\NodeRestrict.config"
"Css" (entire folder)
"fonts" (entire folder)
"img" (entire folder)
"Views\siteTemplate.cshtml" (Select all these files in one go)
"Views\home.cshtml"
"Views\pageArticleItem.cshtml"
"Views\pageBlogList.cshtml"
"Views\pageInner.cshtml"
"Views\pagePortfolioItem.cshtml"
"Views\Partials\SectionProcess.cshtml" (Select all these files in one go)
"Views\Partials\SectionServices.cshtml"
"Views\Partials\SectionStatement.cshtml"
"Views\Partials\SectionTeam.cshtml"
"Views\Partials\SectionTeamGrid.cshtml"
"Views\Partials\SectionTestimonials.cshtml"
"Views\Partials\SectionText.cshtml"
"Views\Partials\BlogCategories.cshtml"
"Views\Partials\BlogPopularTags.cshtml"
"Views\Partials\BlogRecentArticles.cshtml"
"Views\Partials\ContactView.cshtml"
"Views\Partials\IntroHero.cshtml"
"Views\Partials\IntroSlider.cshtml"
"Views\Partials\IntroStatic.cshtml"
"Views\Partials\IntroYoutube.cshtml"
"Views\Partials\NewsletterForm.cshtml"
"Views\Partials\PageBackgroundImage.cshtml"
"Views\Partials\PageBreadcrumb.cshtml"
"Views\Partials\PageFooter.cshtml"
"Views\Partials\PageIcons.cshtml"
"Views\Partials\PageLogo.cshtml"
"Views\Partials\PageMenuTop.cshtml"
"Views\Partials\PageMetas.cshtml"
"Views\Partials\PagePager.cshtml"
"Views\Partials\PageSectionRenderer.cshtml"
"Views\Partials\SectionAccordion.cshtml"
"Views\Partials\SectionActionBox.cshtml"
"Views\Partials\SectionClientLogos.cshtml"
"Views\Partials\SectionContact.cshtml"
"Views\Partials\SectionContentSlider.cshtml"
"Views\Partials\SectionCounter.cshtml"
"Views\Partials\SectionFaq.cshtml"
"Views\Partials\SectionFaqTabbed.cshtml"
"Views\Partials\SectionFeatures.cshtml"
"Views\Partials\SectionImageGallery.cshtml"
"Views\Partials\SectionMultiCol.cshtml"
"Views\Partials\SectionPercentages.cshtml"
"Views\Partials\SectionPortfolio.cshtml"
"Views\Partials\SectionPricing.cshtml"
You can now publish the site to a local instance of IIS using Web
Deploy.
This post was helpful, but I need a "Getting Started" page on how to get uMazel actually up an running. All I need to get started is the home page and I am sure that I can take it from there (with a dozen more questions to follow - LoL).
At any rate, I have Umbraco up; the database is up (SQL Server - hosted); I have forms installed (could that be a problem?); and then I have uMazel installed.
Of course, first swing the website came up (locally from VS2019), but indicated that there was no content. So, I went under admin and added content. A home page was listed as an option, so I chose that route.
After the home page was in place, I tried to run it again (under VS) and now I get an error:
Cannot bind source content type Umbraco.Web.PublishedCache.NuCache.PublishedContent to model type Umbraco.Web.PublishedModels.PageHome.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: Umbraco.Web.Mvc.ModelBindingException: Cannot bind source content type Umbraco.Web.PublishedCache.NuCache.PublishedContent to model type Umbraco.Web.PublishedModels.PageHome.
Source Error: An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
I could post the stack trace if you would like.
Is there a "getting started" page somewhere with a checklist of tasks to perform to get the site up and running? I have used this kit in the past (years ago) and it looks familiar.
I would offer to sign up for consulting services but I am just trying to help and put up a website for a high school reunion with no budget. I like the fact that you integrate with Mailchimp, plus the your cascading menus, so I don't want to go back to the default starter kit.
In an effort to continue, I have restarted the process, except this time I "touched and published" every node under the home page.
Now I get a different error:
Compilation Error
Description: An error occurred during the compilation of a resource required to service this request. Please review the following specific error details and modify your source code appropriately.
Compiler Error Message: CS0433: The type 'PageHome' exists in both 'AppWeball.generated.cs.8f9494c4.13l7kuxr, Version=0.0.0.1, Culture=neutral, PublicKeyToken=null' and 'Umbraco.Web.PublishedModels, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null'
Source Error:
Line 46:
Line 47:
Line 48: public class PageViewsHomePagecshtml : Umbraco.Web.Mvc.UmbracoViewPage
I understand that we are in different time zones, so I am patient. I would like to use the uMazel kit, but I need something up this weekend.
Quick Guide - Visual Studio, Umbraco, Umazel, Publish
Publishing Umbraco with Umazel using Visual Studio was quite the challenge.
I had a long day yesterday and thought I'd share the end result. You can be up and running in a few minutes if you know what you're doing but I had a lot to learn. There didn't seem to be any complete documentation on this process so I learnt a lot by trial and error. There were lots of errors that required research, many wipe the slate and start overs and several separate test installations with and without Visual Studio to compare end results. This is a summary.
There is no guarantee there won't be more bugs related to the EnablePropertyValueConverters issue but this will at least give you a mostly operational version of Umbraco with Umazel to play with.
Visual Studio 2017 Community : Umbraco 7.10.3 : Umazel 1.0.5
Create a new project in Visual Studio. Visual C# | Web | ASP.NET Web Application (.Net Framework 4.5)
Select Empty project and leave all the options unchecked
Right click the project and select Manage Nuget Packages...
Under Browse, search for "UmbracoCMS" and install it.
Run the project using IIS Express
It's OK to modify the web.config to enable debugging. You should setup transforms before going live anyway.
In SQL Server Management Studio, create a new empty database and add a user with db_owner membership.
Back in Umbraco, enter your name, email and password, tick the box to stay updated and click customize.
You'll receive a welcome email from Umbraco with a link to a collection of short videos on document types. You should watch them before playing with Umbraco. It's not super intuitive so the videos will save you time in the long run.
Enter the database details and Continue
Continue with the default machine key.
No thanks, I do not want to install a starter website
You should be presented with the Umbraco CMS backend
Select Developer from the left | Packages | Starter kits | Umazel | Install package | Finish
Close the browser, stop the debug session.
In Visual Studio Solution Explorer, turn on Show all files. (Icon up the top)
Open Views | Partial | SectionText.cshtml
Change this line of code to avoid the invalid cast error caused by the EnablePropertyValueConverters issue
to
Select the project and run it again using IIS Express.
You should see the default front end with the "OK, now what?" header.
Close the browser and stop the debug session.
Back in Visual Studio Solution Explorer with Show All Files still enabled, right click the following folders and files and select "Include in project". Visual Studio seems to magically publish both Umbraco folders without them being included. It knows about Umbraco but not Umazel.
I have no idea why my old account with the same email disappeared but I've just revisited this and it works fine with 7.13.1
I originally wanted to change two steps but could never login.
You need to include the entire scripts folder in the solution and rather than all those individual files listed, just include the entire Views folder.
Instead of changing any code, open "umbracoSettings.config" and change this to false.
This post was helpful, but I need a "Getting Started" page on how to get uMazel actually up an running. All I need to get started is the home page and I am sure that I can take it from there (with a dozen more questions to follow - LoL).
At any rate, I have Umbraco up; the database is up (SQL Server - hosted); I have forms installed (could that be a problem?); and then I have uMazel installed.
Of course, first swing the website came up (locally from VS2019), but indicated that there was no content. So, I went under admin and added content. A home page was listed as an option, so I chose that route.
After the home page was in place, I tried to run it again (under VS) and now I get an error:
Cannot bind source content type Umbraco.Web.PublishedCache.NuCache.PublishedContent to model type Umbraco.Web.PublishedModels.PageHome.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: Umbraco.Web.Mvc.ModelBindingException: Cannot bind source content type Umbraco.Web.PublishedCache.NuCache.PublishedContent to model type Umbraco.Web.PublishedModels.PageHome.
Source Error: An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
I could post the stack trace if you would like.
Is there a "getting started" page somewhere with a checklist of tasks to perform to get the site up and running? I have used this kit in the past (years ago) and it looks familiar.
I would offer to sign up for consulting services but I am just trying to help and put up a website for a high school reunion with no budget. I like the fact that you integrate with Mailchimp, plus the your cascading menus, so I don't want to go back to the default starter kit.
Thanks in advance, -Bobby
In an effort to continue, I have restarted the process, except this time I "touched and published" every node under the home page.
Now I get a different error:
Compilation Error Description: An error occurred during the compilation of a resource required to service this request. Please review the following specific error details and modify your source code appropriately.
Compiler Error Message: CS0433: The type 'PageHome' exists in both 'AppWeball.generated.cs.8f9494c4.13l7kuxr, Version=0.0.0.1, Culture=neutral, PublicKeyToken=null' and 'Umbraco.Web.PublishedModels, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null'
Source Error:
Line 46:
Line 47:
Line 48: public class PageViewsHomePagecshtml : Umbraco.Web.Mvc.UmbracoViewPage
I understand that we are in different time zones, so I am patient. I would like to use the uMazel kit, but I need something up this weekend.
Thanks again, -Bobby
Okay... I am on the road to working with uMazel.
o) I installed ModelsBuilder (nuget).
o) Deleted the Home Page.
o) Uninstalled uMazel.
o) Uninstalled Forms (although I believe that had nothing to do with my problems.
o) Rebuilt the VS Solution.
o) Re-ran Umbraco from VS.
o) Reinstalled uMazel.
o) Rebuilt the VS Solution.
o) Re-ran Umbraco from VS.
And now I get this beautiful message:
Welcome to the uMazel Starter Kit for Umbraco 8
BTW - Nice Shoes!
is working on a reply...