Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Exceptionless.Windows&Wpf for dotnet core 3.0 rc #216

Merged
merged 8 commits into from
Jan 29, 2020

Conversation

rwecho
Copy link
Contributor

@rwecho rwecho commented Sep 20, 2019

Copy windows&wpf project to generate new dotnet core 3.0 version.

@CLAassistant
Copy link

CLAassistant commented Sep 20, 2019

CLA assistant check
All committers have signed the CLA.

@niemyjski
Copy link
Member

@rwecho awesome! Thanks for the pr :). Was there any specific changes needed for core support? I'm wondering what it would take to use the same NuGet package/existing projects as I know we can upgrade the existing via csproj and do multi targeting. I'm guessing you tried this? What issues did you run into? Thanks again

@rwecho
Copy link
Contributor Author

rwecho commented Sep 20, 2019

hi @niemyjski Thanks for your reply.
I was afraid of impating the users using the fx version.
The question I met when modified.

  1. '/Images/ErrorFeedback.png' can found in resource.
    fix with '/Exceptionless.Wpf.Core;component/Images/ErrorFeedback.png'
    I found no reason.
  2. 'CrashReportForm.resx' can found in Exceptionless.Windows.
    fix with add something in the csproj
 <ItemGroup>
   <EmbeddedResource Update="Dialogs\CrashReportForm.resx">
     <SubType>Designer</SubType>
     <DependentUpon>CrashReportForm.cs</DependentUpon>
   </EmbeddedResource>
 </ItemGroup>

And I add new commits : remove dotnet core version && replace windows with multi targeting.

@niemyjski
Copy link
Member

Thanks for your help. I think multi targeting is the best approach. I'll help test this as well :).

@niemyjski
Copy link
Member

I'm just checking in to see how things were going. Did you have any luck merging these?

@niemyjski
Copy link
Member

@rwecho is there anything I can do to help with this pr?

1 similar comment
@niemyjski
Copy link
Member

@rwecho is there anything I can do to help with this pr?

@rwecho rwecho requested a review from niemyjski January 16, 2020 11:45
@rwecho
Copy link
Contributor Author

rwecho commented Jan 16, 2020

@niemyjski Sorry for late reply . I am not familiar with appveyor/cla. It warns me build failed and let me sign the license. I don't know what to do.

I thought you will resolve it . But sorry for ignoring this again.
image

Could you tell me what I should do next ? Thanks.

Copy link
Member

@niemyjski niemyjski left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I left some comments and questions on this review (thanks again for the PR). Do we need to make any build changes for this / maybe simplify the whole build because now the project system can build nuget packages for everything. Also did you run into any issues testing this on .NET 4.5?

@@ -7,7 +7,7 @@
<AssemblyTitle>Exceptionless client for non visual (ie. Console and Services) applications.</AssemblyTitle>
<Description>Exceptionless client for portable applications. $(Description)</Description>
<PackageTags>Exceptionless;Error;Report;Reporting;Exception;Logging;Log;ELMAH;pcl;NETSTANDARD;Core</PackageTags>
<TargetFrameworks>netstandard1.2;netstandard1.3;netstandard1.4;netstandard1.5;netstandard2.0;portable46-net451+win81+wpa81;net45</TargetFrameworks>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we still need to support this, any reason this was removed?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I forgot to add it again. Because I can not compile success on my pc environment.

<SolutionDir Condition="$(SolutionDir) == '' Or $(SolutionDir) == '*Undefined*'">$(MSBuildProjectDirectory)\..\..\..\</SolutionDir>
<RestorePackages>true</RestorePackages>
<TargetFrameworks>netcoreapp3.0;net45</TargetFrameworks>
<UseWindowsForms>true</UseWindowsForms>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What does this do?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

UseWindowsForms label providers Microsoft.WindowsDesktop.App.WindowsForms framework collections.
It's along with project created, same with UseWPF

@@ -5,6 +5,5 @@

[assembly: CLSCompliant(true)]
[assembly: ComVisible(false)]
[assembly: AssemblyTitle("Exceptionless.Wpf")]
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Any reason for removing this?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same to the above AssemblyTitle reason.

@@ -22,7 +26,7 @@
[AppName] has encountered a problem and needs to close. We are sorry for the inconvenience.
</TextBlock>
<Image Name="errorImage" Grid.Column="2"
Source="../Images/ErrorFeedback.png"
Source="/Exceptionless.Wpf.Core;component/Images/ErrorFeedback.png"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Where did this core namespace come from? Is this correct?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I forgot to modify it, when migrating from Exceptionless.Wpf.Core. I'll fix it.

Background="{DynamicResource {x:Static SystemColors.ControlBrushKey}}"
FocusManager.FocusedElement="{Binding ElementName=DescriptionTextBox}"
Icon="../Images/ErrorFeedback.png">
Icon="/Exceptionless.Wpf.Core;component/Images/ErrorFeedback.png"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Where did this core namespace come from? Is this correct?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I forgot to modify it, when migrating from Exceptionless.Wpf.Core. I'll fix it.

@@ -4,6 +4,5 @@

[assembly: CLSCompliant(true)]
[assembly: ComVisible(false)]
[assembly: AssemblyTitle("Exceptionless.Windows")]
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Any reason for removing this?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This will produce error CS0579: Duplicate 'System.Reflection.AssemblyTitleAttribute' attribute. The csproj will generate title attribute same with project name, this should be written in the in the csporj.

duplicate error
msdn about csproj

Copy link
Contributor Author

@rwecho rwecho left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @niemyjski thanks for your patience to give directions. I did some work according to your reviews.

  1. upgrade to .NET Core 3.1
  2. restore portable46-net451+win81+wpa81 for project Exceptionless
  3. fix icons error namespace.

@@ -7,7 +7,7 @@
<AssemblyTitle>Exceptionless client for non visual (ie. Console and Services) applications.</AssemblyTitle>
<Description>Exceptionless client for portable applications. $(Description)</Description>
<PackageTags>Exceptionless;Error;Report;Reporting;Exception;Logging;Log;ELMAH;pcl;NETSTANDARD;Core</PackageTags>
<TargetFrameworks>netstandard1.2;netstandard1.3;netstandard1.4;netstandard1.5;netstandard2.0;portable46-net451+win81+wpa81;net45</TargetFrameworks>
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I forgot to add it again. Because I can not compile success on my pc environment.

<SolutionDir Condition="$(SolutionDir) == '' Or $(SolutionDir) == '*Undefined*'">$(MSBuildProjectDirectory)\..\..\..\</SolutionDir>
<RestorePackages>true</RestorePackages>
<TargetFrameworks>netcoreapp3.0;net45</TargetFrameworks>
<UseWindowsForms>true</UseWindowsForms>
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

UseWindowsForms label providers Microsoft.WindowsDesktop.App.WindowsForms framework collections.
It's along with project created, same with UseWPF

@@ -5,6 +5,5 @@

[assembly: CLSCompliant(true)]
[assembly: ComVisible(false)]
[assembly: AssemblyTitle("Exceptionless.Wpf")]
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same to the above AssemblyTitle reason.

@@ -22,7 +26,7 @@
[AppName] has encountered a problem and needs to close. We are sorry for the inconvenience.
</TextBlock>
<Image Name="errorImage" Grid.Column="2"
Source="../Images/ErrorFeedback.png"
Source="/Exceptionless.Wpf.Core;component/Images/ErrorFeedback.png"
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I forgot to modify it, when migrating from Exceptionless.Wpf.Core. I'll fix it.

Background="{DynamicResource {x:Static SystemColors.ControlBrushKey}}"
FocusManager.FocusedElement="{Binding ElementName=DescriptionTextBox}"
Icon="../Images/ErrorFeedback.png">
Icon="/Exceptionless.Wpf.Core;component/Images/ErrorFeedback.png"
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I forgot to modify it, when migrating from Exceptionless.Wpf.Core. I'll fix it.

@@ -4,6 +4,5 @@

[assembly: CLSCompliant(true)]
[assembly: ComVisible(false)]
[assembly: AssemblyTitle("Exceptionless.Windows")]
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This will produce error CS0579: Duplicate 'System.Reflection.AssemblyTitleAttribute' attribute. The csproj will generate title attribute same with project name, this should be written in the in the csporj.

duplicate error
msdn about csproj

@rwecho rwecho requested a review from niemyjski January 19, 2020 08:47
Copy link
Member

@niemyjski niemyjski left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the PR! We need to test this like crazy before merging which I'll start this process here this week or next (traveling a bunch this week). If you could help test and list the platforms tested that would be a huge help!

@niemyjski niemyjski added help wanted testing Needs Testing and removed investigating labels Jan 21, 2020
@niemyjski niemyjski changed the base branch from master to feature/net-core-wpf January 29, 2020 13:39
@niemyjski niemyjski merged commit dca0334 into exceptionless:feature/net-core-wpf Jan 29, 2020
@niemyjski
Copy link
Member

Thanks for the PR! I merged it into a branch so I can continue testing it and update the build if required.

ejsmith pushed a commit that referenced this pull request Feb 19, 2020
* add winform & wpf for dotnet core 3.0 preview.

* add nuget script

* remove core projects for dotnet core 3.0 and will replaced with fx version.

* replace fx version with multi targeting

* fix obsolete namepsace.

* upgrade .NET Core 3.1

* restore frameworks portable46-net451+win81+wpa81

Co-authored-by: Blake Niemyjski <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

3 participants