Activities of "jholla"

Yes I can connect just fine, ABPBoiler wont connect however

You're over engineering the problem with above solution(s)/proposals:

It is due to a JSON Serialization issue, and there is two ways to fix it by Ignoring Reference Loop Handling, or JsonIgnore Attribute:

Number 1: This was the fix to my issue, add this to Startup.cs inside the public void ConfigureServices(IServiceCollection services) method:

services.AddMvc().AddJsonOptions(options => {
    options.SerializerSettings.ReferenceLoopHandling
      = ReferenceLoopHandling.Ignore;
});

Related Articles on the above:

<a class="postlink" href="https://benohead.com/c-circular-reference-detected-serializing-object/">https://benohead.com/c-circular-referen ... ng-object/</a> ASP.NET Core API only returning first result of list Number 2: If you want to also be able to have your API ready for TCP/IP or MVC/Razor, do not use that and just use the [JsonIgnore] attribute, which is actually a better practice than the code above, see articles below for more info:

<a class="postlink" href="http://www.newtonsoft.com/json/help/html/serializationattributes.htm#JsonIgnoreAttribute">http://www.newtonsoft.com/json/help/htm ... eAttribute</a>

<a class="postlink" href="https://stackoverflow.com/questions/10169648/how-to-exclude-property-from-json-serialization">https://stackoverflow.com/questions/101 ... ialization</a>

Error: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) PM>

COnnection siting in appsettings.json: { "ConnectionStrings": { "Default": "Server=localhost; Database=(localdb)/MSSQLLocalDB/VMARDb; Trusted_Connection=True;" } }

Also tried:

{ "ConnectionStrings": { "Default": "Server=localhost; Database=VMARDb; Trusted_Connection=True;" } }

I get this error after running Update-Database. How can I fix this?

A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

Hello,

Is there a way to generate a new dB instance with every tenant? If that is currently unavail, do you have a resource you can point me to, or a tutorial?

Thanks Much

says page not found, i want to implement this myself

For the .NET Core version, how hard would it be to add a feature that creates a seperate dB for each tenant?

<ins>SEE HERE:</ins> <a class="postlink" href="https://msdn.microsoft.com/en-us/magazine/dn948104.aspx">https://msdn.microsoft.com/en-us/magazine/dn948104.aspx</a>

<a class="postlink" href="http://benfoster.io/blog/aspnet-core-multi-tenancy-data-isolation-with-entity-framework">http://benfoster.io/blog/aspnet-core-mu ... -framework</a>

<a class="postlink" href="http://stackoverflow.com/questions/32865627/using-multiple-databases-with-single-dbcontext-and-entites-and-generating-conn-s">http://stackoverflow.com/questions/3286 ... ing-conn-s</a>

<a class="postlink" href="http://stackoverflow.com/questions/31170814/entity-framework-6-creating-database-with-multiple-contexts">http://stackoverflow.com/questions/3117 ... e-contexts</a>

Where would I implement the logic to verify that strong passwords be made of lowercase letters, uppercase letters, characters and digits. The number of required characters needs to be a min.length if 12 characters, with no maximum length. Passwords must expire every 90 days as well.

Is there any documentation, explanation or resources you can provide links to that would show me how to implement login sessions that expire after 20 minutes of idle time, using IAbpSession?

FOUND THE FIX:

Step 1 targets the x86 platform

<a class="postlink" href="http://www.developerhandbook.com/entity-framework/project-failed-to-build-error-when-adding-an-entity-framework-migration-add-migration/">http://www.developerhandbook.com/entity ... migration/</a>

Step 2 installing TypeScript for Visual Studio fixed it, although TypeScript was already installed globally on my machine via npm

<a class="postlink" href="http://stackoverflow.com/questions/37350183/keep-getting-tsc-exe-exited-with-code-1">http://stackoverflow.com/questions/3735 ... ith-code-1</a>