Hi,
any news about this topic?
Kind regards
Hi aaron,
that is correct, but as it look like it is working only with VS 2017 15.3 as stated also on NET Standard 2.0 announcment page:
The .NET Standard 2.0 specification is now complete. It is supported in .NET Core 2.0, in the .NET Framework 4.6.1 and later versions, and in Visual Studio 15.3. You can start using .NET Standard 2.0 today.
my problem is that i'm stuck with VS 2015 for another 6 months or so and would really like to update my solution to 4.6.0.
Is there anything you can do about this? Would it be possible to still release ABP assemblies for both "frameworks" like you did for version 2.3.0 (netstandard 1.6 and net46)?
hi,
I did try that, but no luck. May I ask you why are you stoped releasing Abp assemblies for 4.6.1 framework?
kind regards
Hi @alirizaadiyahsi,
thank you for your support, but we are not working with NET CORE and therefore I don't see any reason why we need to suddenly use/buy a new licenses for VS 2017.
@ismcagdas: Any idea how to get it to work in VS 2015?
Kind regards
Hi,
no, we are using VS 2015 14 Update 3.
Hi @hikalkan,
statistic data you are having/showing can be very misleading. Probablly everyone has downloaded Aspnet Core version, even I did (several times). And that was only few months ago, in April I think. But then I realized that the solution was not even close to be ready for a serious commercial project (lack of documentation, a lot of bugs, …).
Because of that I decided to go with AspNet Angularjs and now, few months later, you are telling me that you are not planning to implement any new features into this solution. I’m very disappointed I must say …
At least you should implement features which are normally supported in ABP, like disabling languages and such ….
Kind regards
Hi @ismcagdas,
I'm not quite sure what you mean with "We didn't implement IsDisabled in ABP actually.", because you did implement this in ABP. This change came with v4.1.0.
What you didn't do is the implementation in AngularJs 1.x (which you should btw).
Because I think that this is a “MUST HAVE” of every system, I've implemented it on my own. So now only enabled languages are visible (frontend, login and backend) and admins can enable/disable languages as they want.
But then I found out that the user can still see UI in a language which is disabled. And that is not what I understand as “IsDisabled”.
Normally an entity (in this case language) is disabled for a reason. I think that if user still has this language stored in his cookie, it should be ignored and user should get UI in default language.
Do you agree?
Hi @ismcagdas,
I'm very glad to hear that.
While you are at it could you also check if it is possible to set a user UI language to default one if current user UI language is disabled?
I have a situation where user UI language is set to "de" (value is stored in Abp.Localization.CultureName cookie) even if this language is disabled.
Thank you.
But i have another question .....
Could you please tell me why is property "isDisabled" in "abp.localization.languages" set as string and not as boolean?
Hi,
you are the best!!!
Thank you for your support.
kind regards
