Upgrading umbraco from 4 to 6 - mysql

I would like to install Umbraco 6.1.x, but my host suffers from this issue: http://issues.umbraco.org/issue/U4-1632
Basically, I can't install 6 due to an incompatibility with MySQL on Linux and Umbraco 6, but I read that I can upgrade from 4.x.x and then upgrade to 6. The question is, how do I do that? I.e. what files do I need to upload and edit such that the database remains, but all umbraco files are version 6?

Yes, according to the bug report you can install a Umbraco v4.11.x and then upgrade this to v6.1.x and this should work fine.
The downloads are all available here: http://our.umbraco.org/download
However, the easiest way to get Umbraco set up is to use NuGet in Visual Studio. So you could run the following line from the NuGet console:
Install-Package UmbracoCms -Version 4.11.10
You'll have to use the console for this because if you use the Package manager, it will just install the latest Umbraco package version.
Next, load your site in a browser and configure the database settings. Then upgrade using NuGet again. I find the easiest way to do this is to open the NuGet package manager in Visual Studio, select "Updates", find the Umbraco package and click "Update". This will automatically update all the files for you.
You will then need to load up the site again, at which point it will prompt you to upgrade, and you can just follow the steps in the wizard.

Related

I cannot install Blazorise in my Blazor server side app. I get the Error that "Microsoft.AspNetCore.Blazor" package could not be find

I have a blazor server side app that is working without problem. (Net Core 3.1). I tried to install Blazorise according the quick start page in https://blazorise.com/docs/start. As my server has no internet access I have downloaded the packages "Blazorise.Bootstrap 0.7.2" and "Blazorise.Icons.FontAwesome 0.9.2.5".
I can install the "Blazorise.Icons.FontAwesome" without Error. But if I try to install "Blazorise.Bootstrap" I get the Error
"NU1101: Unable to find package Microsoft.AspNetCore.Blazor. No packages exist with this id in source(s): Microsoft Visual Studio Offline Packages, Package source"
I cannot find any package like "Microsoft.AspNetCore.Blazor". What should I do now?
Update1:
I have found a package like "Microsoft.AspNetCore.Blazor.Templates 3.1.0-preview4.19579.2" but if I try to install I get Error
"Package 'Microsoft.AspNetCore.Blazor.Templates 3.1.0-preview4.19579.2' has a package type 'Template' that is not supported by project 'WebApplication7'"
I had some problmes at the beginning with updateing NetCore3.1 to Net6.0 But at the end I fixed them. So I could install Blazorise's last version without problem.
Thanks for the comments, suggesting that.

Can't get TeamCity to use C# 7.1 - but works manually using msbuild

I have TeamCity 2019.1.5 with most recent Visual Studio Tool 2017 installed:
I have a project which uses C# 7.1 features, and it compiles locally just fine in VS 2017, and I made sure it has <LangVersion>latest</LangVersion> in CSPROJ file. But when I run it from TeamCity (agent is on the same server) with the following build step:
it fails with the following error in the logs:
[Csc] Services\MappingService.cs(1942, 40): error CS8107: Feature 'default literal' is not available in C# 7.0. Please use language version 7.1 or greater.
If I start VS2017 command prompt on the server and go to the project's folder and run msbuild tt.csproj /target:Rebuild it works fine: compiles and I do not get any errors. Needless to say, if I remove C# 7.1-specific code, everything works in the current configuration.
I installed Visual Studio Tool 2019 and with MSBuild 16 it works without any problems as well. But I prefer to use 2017 tools so both server and dev environments are the same. What can cause this issue?
I had this problem and fixed it by fixing the solution configuration in the build step configuration. It needs to be set to either "Debug" or "Release". Mine was set to a parameter, which resolved to something other than one of those values.

The target "ResolveTagHelperRazorGenerateInputs" does not exist in the project

I am getting the following error when i try to build an AspNetCore Web Application targeting netcoreapp2.2.
Error MSB4057 The target "ResolveTagHelperRazorGenerateInputs" does not exist in the project. C:\Program Files\dotnet\sdk\2.2.103\Sdks\Microsoft.NET.Sdk.Razor\build\netstandard2.0\Sdk.Razor.CurrentVersion.targets
I have tried the following:
clear cache on vs according to this post
update vs2017 to 15.9.5
reinstall net core sdks
reinstall vs
Nothing helped. I first got the error during an upgrade from core 2.1 to core 2.2 on a different project, and it's possible that by mistake edited the
Sdk.Razor.CurrentVersion.targets file. From that moment on, i keep getting this error on any project that targets core 2.2 (even new ones).
Does anyone encountered this problem or have any clues about solving it?
Thanks
After long battles it figured out to be a problem with VS NuGet Package Manager.
All I had to do was:
VS > Tools > Options > NuGet Package Manager > Clear All NuGet Cache(s).
The Following Link was my solution. I also struggled to get this fixed.
Just copy the files from the NetStandard2.0 folder from GitHub then replace it with you Directory from the same location.
Hopefully this helps someone.!
Here is the Answered Link:
https://social.msdn.microsoft.com/Forums/en-US/cafc9823-eb61-46f7-8489-007242ef2ad2/target-quotresolvetaghelperrazorgenerateinputsquot-does-not-exist-in-the-project?forum=msbuild
Here is the GitHub Link
https://github.com/aspnet/Razor/tree/master/src/Microsoft.NET.Sdk.Razor/build/netstandard2.0
I encountered the same issue during the Azure build pipeline process, and clearing the NuGet package cache resolved the issue.
Solution:
I used a dotnet tasks with "custom" to issue the following command before NuGet package restore task:
command:
dotnet nuget locals global-packages -c
Screenshot shows the build pipeline task
For me the solution was as follows:
In Visual Studio
Right click on each project and click "Unload Project"
Right click on each project and click "Reload Project"

Specified Gradle Installation (..) is not supported by this tooling API version (1.6, protocol version 4) [duplicate]

This question already has answers here:
Gradle build errors with Android Studio
(3 answers)
Closed 9 years ago.
I have just set up Android Studio 0.2.2 and updated my Android SDK to the latest version.
I have exported my Android project (android:minSdkVersion="8", android:targetSdkVersion="15") in Eclipse by 'Generate Gradle Build Files' without (visible) problems. And I can export/compile my app in Eclipse just fine, it also runs fine in the emulator.
However, in Android Studio, when trying to import my project, I am confronted with the above error message. "Gradle Home" is (IMO, correctly) displayed as "D:\Prog\Android-Studio\plugins\gradle".
Any idea how to make Android Studio feel more comfortable on my computer?..
I've encountered a similar problem where I can't import my project. There is at least one answer out there that may help; it requires the creation of a blank project in Android Studio and then copy files over from Eclipse. This ensures the creation by Android Studio of the necessary Gradle files, etc. Here's the link to the full answer: Gradle build errors with Android Studio
Look's like you should try to use the Gradle Wrapper rather than a local Gradle distribution. According to Gradle's website (http://www.gradle.org/docs/current/userguide/gradle_wrapper.html):
The wrapper is something you should check into version control. By distributing the wrapper with your project, anyone can work with it without needing to install Gradle beforehand. Even better, users of the build are guaranteed to use the version of Gradle that the build was designed to work with. Of course, this is also great for continuous integration servers (i.e. servers that regularly build your project) as it requires no configuration on the server.
You'll need to mimic the following structure in your project's directory:
simple/
gradlew
gradlew.bat
gradle/wrapper/
gradle-wrapper.jar
gradle-wrapper.properties
At that point, go to Settings (Windows) Preferences (Mac), click "Gradle" on the left hand side, choose "Use Gradle wrapper (recommended)". If that option isn't available, try restarting Android Studio or closing and reimporting your project. Checking this option should ensure that you always build with the correct Gradle distribution.

Nuget, Castle Windsor Client Profile vs Full Profile

I'm trying to use Castle Windsor with Log4Net facility. I've installed the packages through Nuget.
The requirement for this to work is to use Full profile Castle.LoggingFacility. Nuget referenced the Client Profile version.
How can I force Nuget to install the Full profile version?
I might be wrong but it sounds like the issue with the target framework setting on your project:
for Castle.Windsor to work it has to be set to .NET Framework 4 rather than to .NET Framework 4 Client Profile.
You can configure it by opening project properties, tab Application (in Visual studio) or just editing the project file.
If that's about the version of the package after all, then usually using NuGet you can append a flag install-package Castle.Windsor -version 2.5.3 to specify which one to install, but I couldn't find any options there when it comes to Castle.LoggingFacility.
I had the same problem earlier and I think you should check your packages.config file. There could be targetFramework="net40-client",
which points NUGet to the packages\Castle.LoggingFacility.3.2.0\lib\net40-client directory.
Simply change it to net40 and all's done.