Caliburn.Micro icon indicating copy to clipboard operation
Caliburn.Micro copied to clipboard

Caliburn.Micro issue

Open Jankiasati opened this issue 1 year ago • 10 comments

Hi Team,

I am working on dot net project where i migrated my dot net framework 4.6.1 to 4.8 along with visual studio 2015 to visual studio 2022.

when am doing so am getting warning for few project component. I attached the warning SS.

I tried to upgrade Nuget package(Caliburn.Micro and Caliburn.Micro.Plateform) , Caliburn.Micro.Plateform is getting upgraded to latest version but Caliburn.Micro is not getting upgraded to latest version.

I have caliburn.Micro library which is targeting 4.5 dotnet version when i try to change the target from 4.5 to 4.8.

4.8 dotnet fraemwork is not getting listed in dropdown.

could you help me. Target Framework

Jankiasati avatar Oct 17 '24 13:10 Jankiasati

Screenshot 2024-10-18 104626

Jankiasati avatar Oct 18 '24 05:10 Jankiasati

Are you using Caliburn.Micro.Core as the nuget package? https://www.nuget.org/packages/Caliburn.Micro.Core

vb2ae avatar Oct 18 '24 12:10 vb2ae

No, we would like to know which version of caliburn.Micro is compatible with .net 4.8 framework.

Jankiasati avatar Oct 21 '24 04:10 Jankiasati

~~the current version of Caliburn.Micro is compatible with .net framework 4.8. What I recommend is uninstalling caliburn.micro and Caliburn.Micro.Platform and install Caliburn.Micro.Core. Installing Caliburn.Micro.Core will also install the proper version of Caliburn.Micro. I suspect the error is version mismatch with Caliburn.Micro.Platform~~

vb2ae avatar Oct 21 '24 23:10 vb2ae

Actually I am seeing the same warning in the Features.Wpf sample app. Do you have this warning about System.Net.Http also?

image

vb2ae avatar Oct 22 '24 11:10 vb2ae

No, I did not get the error which you have mentioned.

When we are upgrading to latest version of Caliburn.Micro(4.0.212) it is adding Caliburn.Micro.Core ,Caliburn.Micro.PlateForm.Core Package references.

And it's keeping our existing Package references Caliburn.micro to the older version(2.0.0.5) and only upgrading Caliburn.Micro.Plateform to the latest version 4.0.0.0

After that if am building my project am getting following errors. the type "sample " exist in both caliburn.micro , verson = "2.0.0.5" and caliburn.micro.core , version =="4.0.0.0".

if am removing caliburn.micro and keeping caliburn.micro.core refrences to my project am getting the error which i added below. Error SS1

And if am keeping caliburn.micro and removing caliburn.micro.core to our project we are getting the error which i added below.

Error SS2

am trying to migrate dotnet framework version from 4.6 to 4.8.1 and we are not migrating to .net core version. so please tell us which caliburn.micro package is compatible with .net 4.8.1 framework.**

if we are going with the latest versions it is breaking our existing changes as function signature is changed to async

Jankiasati avatar Oct 24 '24 08:10 Jankiasati

Started with a new wpf app and added Caliburn.Micro 3. I then upgraded Caliburn.Micro to the latest. This is what I see in packages.config

<?xml version="1.0" encoding="utf-8"?>
    <packages>
    <package id="Caliburn.Micro" version="4.0.212" targetFramework="net48" />
   <package id="Caliburn.Micro.Core" version="4.0.212" targetFramework="net48" />
   <package id="Microsoft.Xaml.Behaviors.Wpf" version="1.1.19" targetFramework="net48" />
 <package id="System.Runtime.Serialization.Primitives" version="4.3.0" targetFramework="net48" />
</packages>

What is in your packages.config? Wondering if maybe there is something that requires the old version of Caliburn.Micro which prevents the upgrade to the newer version

vb2ae avatar Oct 25 '24 21:10 vb2ae

Hello, My configuration is also same. Could you check is it adding Caliburn.Micro references in your project with latest version because my configuration is getting updated but it's not adding reference to the project.

Jankiasati avatar Nov 04 '24 08:11 Jankiasati

Hi.. Please clarify.

Jankiasati avatar Nov 11 '24 13:11 Jankiasati

After you try and update caliburn.micro look in the output window output for package manager. Is there anything saying it could not update the package with a reason

vb2ae avatar Nov 11 '24 17:11 vb2ae