Would like to know as well. We're trying it now in a new project. We are having some trouble with Structuremap. It says .Container is depricated and we should use .StructureMap(). This method needs a new version of Structuremap but this is not supported by Episerver so it seems.

Not quite sure if this is related to us using .NET 4.7 however. Just want to know if there are others with this issue while using 4.7.

Hi Eric,

I didn't experience any issues after upgrade to .net 4.7

I have not experienced any problem so far either but it would be great if we could have an system req update or something telling it support this version. Some customers or their hosting require these "official" documentation sadly :)

We are expereiencing as slow down on performance after upgrading. The same shopping cart page used to take .5 seconds to load and now it is like 4 seconds. 

Wondering if there is any caching issue with this version? 

Thanks, 

Syed 

Syed,  Is your problem related to upgrading to .NET 4.7, or to a new Commerce version?  If Commerce, to which version did you recently upgrade?

Lindy. that you should use .StructureMap() have nothing to do with .NET 4.7 or a newever version of StructureMap. The .StructureMap() is an extension to ServiceConfigurationContext that episerver have made in the Episerver.Framework lib.

So when you inherit from IConfigurableModule and in the ConfigureContainer function, you should use

context.StructureMap().Configure(c =>
{
//something
});

instead of 

context.Container.Configure(c =>
{
//something
});

We are seeing big slowdown in performance the application is swithed to .net framework 4.7. Same EPI Version. 

THanks, 

Syed 

.

@Sebastian

I believe it has something to do with the new version of Episerver: it required me to update Structuremap but Episerver cannot work with this newer version of Structuremap. It took me some time but after a while I managed to get it working and it didn't say it was depricated anymore. I'm not quite sure how it came to be that it started working again all of a sudden.

Syed, Which version of Commerce are you using?

Hi Bob, 

We are using 10.10.

I think the issue is with caching. Microsoft .net 4.7 has some issue with caching  https://support.microsoft.com/en-us/help/4035412/fix-expiration-time-issue-when-you-insert-items-by-using-the-cache-ins 

Working with EPI's support team to see what can be done.

Thanks, Syed 

Having same big issues with caching. Don`t move to 4.7 if you can, wait for the patch from MS!

http://vimvq1987.com/2017/08/episerver-caching-issue-net-4-7/ 

This might be helpful to you 

I came here to post the very same thing. I'm working on a performance issue and couldn't understand why I was getting cache misses locally, but not in production or uat.

Safe to use 4.7 now?

If you are on CMS Core 10.10.2 or 9.12.5 then this specific caching issue is resolved. 

EDIT: Checked with QAs, we already tested with .NET 4.7, so it should be supported