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

C1 CMS v6.10 #760

Merged
merged 22 commits into from
Oct 5, 2020
Merged

C1 CMS v6.10 #760

merged 22 commits into from
Oct 5, 2020

Conversation

napernik
Copy link
Contributor

@napernik napernik commented Oct 2, 2020

No description provided.

burningice2866 and others added 22 commits April 14, 2020 19:03
…ate it using CodeDomProvider.CreateProvider. This gives the flexibility to configure dynamic compilation via app/web.config, ie. using Roslyn for newer C# features.

Implements feature #735
Integrated CodeBasedFunctionProvider into C1
Extended MethodBasedFunction to be reusable;
Rename ServiceFunctionProvider into CodeBasedFunctionProvider (have not found better name, and since we execute functions both from ServiceLocator and Activator,  and direct call, somehow should be renamed)

Co-authored-by: Taras Nakonechnyi <[email protected]>
Use ActivatorUtilities.GetServiceOrCreateInstance instead of ServiceLocator.GetService + Activator.CreateInstance since the type in question might not be registered in the ServiceContainer but still require services to be injected into its ctor
(by Pauli Østerø )
Making some of the page route related classes reusable
Added possibility to extend SitemapNavigator

Co-authored-by: Taras Nakonechnyi <[email protected]>
#750)

* Get actions from IElementActionProvider loaded via DependencyInjection
#752)

* DataReferenceTreeSelector:Take data for PageReference from SitemapNavigator instead DataFacade.GetDataByUniqueKey
-fix language issue
-fix not synced resx
-fix html encode
-add user-select for name and value
Change hardcoded usage of Microsoft.CSharp.CSharpProvider to instantiate it using CodeDomProvider.CreateProvider
Usage of JsonConvert.SerializeObject should not rely on default JsonSerializerSettings
@napernik napernik merged commit b918360 into master Oct 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants