We have multiple customers (tenants) whose employees do not always have an email address. How can we create a user with UserManager with an optional (null) email address?
We found the problem. It was the changes to SimpleStringCipher. We had data (connection strings) already encrypted in the prior method and that prevented us from logging in. We are now going to set up Feedly.com to watch the github source for this file so we will know when changes are. Thank you for your help.
The log file is attached. The error is:
naries.DictionaryBasedLocalizationSource - Can not find 'SetupOther' in localization source 'AbpZeroTemplate'!
ERROR 2017-09-13 08:21:43,161 [8 ] mplate.Web.Controllers.AccountController - Padding is invalid and cannot be removed.
System.Security.Cryptography.CryptographicException: Padding is invalid and cannot be removed.
We don't know what could have caused this on our side. We welcome any suggestions. Thanks Logs.zip
We are having a similar problem. Can you post the answer to this thread so the rest of us can learn from it?
Thanks
We tried to upgrade our existing project and it will build. When we run, we cannot log in anymore. It gets to the [Post] Action of AccountController and then into GetLoginResultAsync's first line:
var loginResult = await _logInManager.LoginAsync(usernameOrEmailAddress, password, tenancyName);
When stepping through the code, this loops infinitely through our host DB context, ABpZeroTemplateHostDbContext.cs's constructor:
public AbpZeroTemplateHostDbContext(string nameOrConnectionString)
: base(nameOrConnectionString)
{
}
Then we get the generic error message. We have tried to troubleshoot this to the best of our ability for days and have not figured out what could be going on. Screenshots are attached. We thought this might be connected to the reference errors, but maybe it is two separate issues. Is there any way to debug further? screenshots.zip
Hello,
We saw the update to ABP Zero to go to 3.0. We cloned a new version and tried to build we get many reference errors. There is a screenshot attached of the references in the Application project. When we try to upgrade via nuget to ABP 3.0.0 we also get these errors. We are using the .Net 4.6 template (not Core). We started by trying to use git to merge changes with the commit of 93fb08209b96264527ac357163a8f78605913efa and also got these errors. We tried on two different development PC's and still get these errors. We are running VS 2017 version 15.3. Do you have any suggestions on how to resolve this?
Now that Metronic 5 is out [https://themeforest.net/item/metronic-responsive-admin-dashboard-template/4021469]), are there plans to upgrade to it? We would like to upgrade to jquery 3.x but we think Metronic was the bottleneck. Would it be possible in the future to upgrade Abp to only need jquery 3.x?
Thanks!
if the database or database server specified in the connection strings of the web.config file cannot be found, we would like to redirect to a more graceful error page. The error will first appear for us in global.asax.cs > Session_Start > RestoreUserLanguage.
I can trap the error by doing something like this inside a try-catch
SqlConnection connection =
new SqlConnection(ConfigurationManager.ConnectionStrings["Tenant"].ConnectionString);
connection.Open();
: if this fails, then I would like to redirect/transsfer/execute something to get to a Error/NoDb. I have an ErrorController.cs with this view, but cannot figure out if it is possible to get there because the database does not exist. Is this possible with ABP.Net Zero?
The issue has now been resolved.
It was a stupid mistake while the test was mocking an ISettingManger. The production code was constructor injecting a SettingManager.
Altering the production dependency to inject an ISettingManger resulted in the expected behavior.
Thanks for your time.
Dear @alper,
Using the guidance from the Asp.Net core project.
I tried just replacing the mocking container using NSubstitute from AutoFixture.AutoMoq as per the example, see below.
// _settingManager = fixture.Freeze<Mock<ISettingManager>>();
_settingManager = Substitute.For<ISettingManager>();
fixture.Inject<ISettingManager>(_settingManager);
I'm still getting the Parameterless constructor error in SettingDefinition (see SettingDefinition_Parameterless_Ctor.png).
When we started a year plus ago with Apb Zero we created some custom database contexts. This is because of the great feature of Single Deployment with Multiple Databases which fits our needs exactly (see Custom_DbContexts.png).
For better or worse we struggled using AppTestBase class and abandoned deriving from it for our custom tests.
So I'm going to need to spend a little time to research reintegrating or creating a new base class to take advantage of LocalIocManager and Component from the aforementioned example you provided.