MarimerLLC/csla

Version 4.7.101 is a bugfix release over 4.7.100. Release notes for 4.7.100 are below.

Version 4.7.101

• #832 Change NuGet targets from net46 to net461
• #836 BUG: Fix non-generic ConnectionManager
• #834 BUG: Csla.Web.Mvc4.dll for .NET461 reports version 1.0.0.0
• #844 Update samples to CSLA .NET 4.7.101 (thanks to tfreitasleal)

Version 4.7.100

I am pleased to announce the release of CSLA .NET version 4.7.100 with full support for netstandard 2.0 and .NET Core 2.

The packages are now in NuGet. Once some final updates to the samples are complete and merged into master I'll create a formal release tag/page on GitHub.

This release also includes some other very exciting capabilities, including:

• #760 Add support for ASP.NET Core 2.0
• #759 Add support for EF Core (EntityFrameworkCore)
• #813 Major performance improvement when data binding to large object graphs thanks to keithdv
• #795 Add Transactional attribute back into netstandard 2.0 code
• #800 Changes to configuration so it is possible to configure CSLA without any web.config or app.config files (such as in .NET Core, etc.)
• #496 Support ClaimsPrincipal via new CslaClaimsPrincipal type
• #729 ApplicationContext now defaults to using AsyncLocal to maintain values on the current thread/context with help from j055 BREAKING CHANGE
• #712 Support in-place deserialization of an object graph
• #748 Major improvements to serialization via MobileFormatter thanks to jasonbock
• #763 Update to samples thanks to tfreitasleal
• #688 Get ApplicationContext.User authentication working with ASP.NET Core thanks to dazinator
• #766 Update to use latest UWP libraries for Windows 10 Fall Creators Update BREAKING CHANGE
• #790 BUG: Fix AmbiguousMatchException in data portal thanks to iherwald
• #710 BUG: Fix ambiguous Save method issue thanks to rabidkitten

There are a couple known issues with this release:

• #818 Xamarin projects using System.Data.SqlClient show a warning about this assembly's location
• #794 UWP projects show warning PRI263: 0xdef01051 messages relative to CSLA resource strings
• #822 There are two "sets" of CSLA packages/assemblies: one for full .NET 4.6.1+ and one for netstandard (including Xamarin, UWP, .NET Core, etc.) due to a type error between netstandard and full .NET
• #703 Though netstandard supports BinaryFormatter, that is currently not an option from the CSLA configuration, and this needs to be addressed

Regarding the NuGet/assembly split noted in #822:

Right now there are two "families" of CSLA .NET packages in NuGet. One that supports full .NET and one that supports all other runtimes.

The full .NET family must be used for the following types of app:

• Windows Forms
• WPF
• ASP.NET (other than Core)
• Console apps (other than Core)
• Azure Functions
• Any other runtime hosted by full .NET 4.6.1+

The netstandard family must be used for the following types of app:

• Xamrin
• UWP
• .NET Core
• ASP.NET Core
• Any other runtime not hosted by full .NET 4.6.1+

What this means for you is that if your n-tier app is 100% full .NET or full netstandard then you can live within one of those families. BUT if your server is full .NET and your client is Xamarin (for example) then your business library assemblies need to be compiled twice: once for full .NET and once for netstandard.

The Samples\ProjectTracker app shows how this is done by using a Shared Project to contain the code, and two concrete class library projects that compile the code for full .NET and netstandard respectively.

Bug fixes from 4.6.600.

• #745 SerializationInfo.GetValue: _bindingEdit" error - UWP
• #744 Issue with Serializable, SerializableAttribute UWP
• #742 Problem with UWP's SerializationInfo
• #739 WcfProxy consistently uses DefaultBinding if enabled
• #735 Fix missing resources in netstandard 1.6
• #737 Fix serializable attribute issue in UWP BREAKING CHANGE (workaround)

Version 4.6.600 release information:

This release is focused primarily on supporting .NET Core and NetStandard 1.6. There are also a number of bug fixes, enhancements, and improvements to some samples.

This release is available via NuGet.

CSLA .NET v4.6.500 supports the following platforms:

• .NET 4.0, 4.5, 4.6
• .NET Core via netstandard1.5 and netstandard1.6
• Xamarin iOS
• Xamarin Android
• Xamarin PCL (Profile111)
• UWP

Change highlights:

• #733 Remove WinRT packages from NuGet - CSLA no longer supports Win8 development as of version 4.6.600 BREAKING CHANGE
• #722 Add support for ASP.NET Core
• #708 Csla.AspNetCore.Mvc implementation
• #725 Update samples
• #701 Windows Forms now stores Csla.ApplicationContext.User in a static field instead of per-thread BREAKING CHANGE
• Provide More Information in UndoException #472 (#718) BREAKING CHANGE
• RegisterProperty overload (propertyLambdaExpression
• Fix wrong role name in ProjectTracker Sample MockDb (#715)
• Mark SingleCriteria as obsolete #656 (#716)
• Update NuGet targets/dependencies (#713)
• #707 Add editorconfig file for solution (#714)
• #691 Update for VS 2017 (#706) BREAKING CHANGE FOR FRAMEWORK DEVS
• Samples/ProjectTracker Code fixes (#699)
• Fix PropertyConvert of nullable type to nullable enum property. #692 (#695)
• Fix DynamicBindingListBase constraint is missing Csla.Serialization.Mobile.IMobileObject #689 (#690)
• Delete Silverlight dependencies. (#685)
• Fix Sample ExtendableWcfPortalForDotNet (Rolodex) #678 (#683)
• CslaFastStart LastName update fix (#682)
• #680 Fixes trivia issue (#681)
• Allow SerializableAttribute on Enums (#672)
• Add fast start sample and readme (#670)
• Fixes #664 - Add logic to also ConvertFrom TypeConverter inside CoerceValue (#665)
• Throwing exception when sync dataportal tries to call async method on client (#643)

The primary focus of this release is the addition of support for .NET Core 1.0. This was accomplished by adding a NetStandard 1.5 project to the solution, with the output being part of the CSLA-Core NuGet package.

CSLA .NET v4.6.500 supports the following platforms:

• .NET 4.0, 4.5, 4.6
• .NET Core 1.0 via netstandard1.6
• Xamarin iOS
• Xamarin Android
• Xamarin PCL (Profile111)
• UWP
• WinRT and WinRT Phone (this is the last version that supports these platforms)

Here are the changelog highlights:

• #651 Remove iOS Classic projects from solution
• #634 Set PropertyStatus state when source is null (#637)
• #629 Update to latest nuget tooling
• #629 Fix issue with IsSerializable in netstandard
• #626 Ignore resx files copied into netstandard project
• #626 Properly embed default resx file into Csla.dll
• #618 Restore sync DataPortal methods to interface for .NET Core (#620)
• #605 Remove netcore50 project from solution and NuGet output (#609)
• #398 Clean up and fix Model property for Xamarin (#599)
• #590 Updated german resource file

This release is focused primarily on enhancing the existing Xamarin support. There is now a Csla.dll targeting PCL Profile111, which is the current profile for Xamarin.Forms projects and .NET Core.

There is also now a CSLA-Xamarin NuGet package that includes a Csla.Xaml.dll with support for Xamarin.Forms. This includes the same viewmodel base classes as the other XAML platforms, and an implementation of the PropertyInfo control tailored for use in Xamarin.Forms.

@JasonBock added even more analyzers for Visual Studio 2015 to help developers avoid common coding mistakes when building CSLA .NET business classes.

We now have support for the prerelease of Entity Framework 7.

The pt and pt-BR resources for Csla.dll have been updated. Other languages need updates as well - please contribute if you are a native speaker!

There is a new way to customize the server-side data portal by implementing an interceptor that is invoked via the new DataPortalBroker. (#564)

This release is available via NuGet.

• #608 Fix/enhance Source and Value property in Csla.Xaml.PropertyInfo control
• #550 Add Xamarin.Forms support in Csla.Xaml
• #568 Add PCL support for Profile111 (Xamarin.Forms and .NET Core)
• #457 Analyzer: Find Usages of Non-Serializable Types
• #458 Analyzer: Catch when Save() is Called on Itself
• #553 Analyzer: Address => Property Syntax in Analyzers
• #555 Analyzer: Fix Issue with Partial Classes in Analyzers
• #518 EF7 Support
• #539 Fix WinRT bug with OnDeserializedHandler
• #576 Update Resources pt and pt-BR
• #564 Add DataPortalBroker to allow DataPortal Interception
• #574 Fix issue with HttpProxy and Xamarin

Summary of updates since 4.5.x

You can see the change logs for the 4.6.x releases:

• 4.6.100
• 4.6.200
• 4.6.300
• 4.6.400

There are some important non-technical or semi-technical enhancements, including:

• From version 4.6.300 CSLA is now under the MIT license
• Code of Conduct document for contributors and people participating in this forum
• CI server using Appveyor (and a private one using VSTS)
• Now using ZenHub to better track/manage issues and backlog
• Attach gitter site to this forum for any real-time chats we all might want to enjoy

At a high level the technical enhancements include:

• Move all code to a unified set of shared projects - no more "dangling" code files in platform-specific folders, making maintenance easier and cross-platform consistency higher
• Add .NET 4.6 support
• Update to latest version of Xamarin
• Add .NET Core 1.0 support
• Add ASP.NET Core 1.0 support
• Add several analyzers for VS15 that help improve coding quality
• Add support for custom serialization formatters
• New LazyGetProperty and LazySetProperty methods to simplify lazy loading of values
• Support new Serialized and other implementations in Xamarin and UWP
• All platforms now support HttpProxy talking to an HttpPortal endpoint
• Various bug fixes

What was removed?

• Support for Silverlight
• Support for Windows Phone 7 (Silverlight)