Problem solved! The problem occurred because apparently by default, in Json's options have a precaution to avoid referral looping.What I did then was ignore that, as follows:At the Startup of my project, in ConfigureServices inseri:services.AddMvc().AddJsonOptions(options => { options.SerializerSettings.ReferenceLoopHandling = ReferenceLoopHandling.Ignore; }); Get the solution https://stackoverflow.com/questions/42577248/web-api-returns-only-one-child-object-from-one-to-many-relationship-using-entity But now I have another question: Is it wrong to do that? Since I am globally disabling a "precaution"!

Just use the question mark on the parameter that can be optional. In the example below id would be optional.app.UseMvc(routes => { routes.MapRoute("default", "{controller=Home}/{action=Index}/{id?}"); });

You can do without using ajax as belowView Index<a href="#deleteEmployeeModal" class="delete" data-toggle="modal" data-id="@item.Id"><i class="fas fa-trash" data-toggle="tooltip" title="Delete"></i></a> <!-- Delete Modal HTML --> <div id="deleteEmployeeModal" class="modal fade"> <div class="modal-dialog"> <div class="modal-content"> <div class="modal-header"> <h4 class="modal-title">Deletar Chamado</h4> <button type="button" class="close" data-dismiss="modal" aria-hidden="true">&times;</button> </div> <div class="modal-body"> <p>Tem certeza que deseja deletar este chamado?</p> <p class="text-warning"><small>Está ação não tem volta!</small></p> </div> <div class="modal-footer"> &lt;form asp-action="Delete"&gt; &lt;div class="form-actions no-color"&gt; &lt;button type="button" class="btn btn-danger" data-dismiss="modal"&gt;Cancelar&lt;/button&gt; &lt;button type="submit" value="Delete" class="btn btn-primary" /&gt; &lt;/div&gt; &lt;/form&gt; &lt;/div&gt; &lt;/div&gt; </div>Just direct the form post to your "Delete" action in the controller.

I found the solution:if (ModelState.ContainsKey("Input.Card")) ModelState.Remove("Input.Card");

Hello Thiago Correia blz? Look, I'd need more information to analyze your problem and give you an accurate answer. However, I have experienced problems similar to Query's assembly or even the Bank's structure.1o - Assemble the pure query in the hand and give the Insert straight in the bank to check if the structure is ok.2nd - Always debuga and take the query result and compare with the Bank's.3o - Also note that the input that is instantiated is actually passing value on your submit. A tip! Uses a design patterns called Factory, avoids a lot of writing and helps keep the code clean. Embraces!

It is not a matter of route: it is a matter of making all controllers protected by a standard authorization filter. Once all controllers are protected, all accesses will be redirected to the login page. Only after login controllers can be accessed.For this, change the method ConfigureServices in its class Startup:From:services.AddMvc(); To:services.AddMvc(options => { var policy = new AuthorizationPolicyBuilder().RequireAuthenticatedUser().Build(); options.Filters.Add(new AuthorizeFilter(policy)); }); If you want some control to be displayed by unsutained users, just use the annotation [AllowAnonymous] as usual:[AllowAnonymous] public IActionResult Index() => View();

You can use from the version of Ef Core 2.2For this you need to install the following Nuget packages if you use Sql Server:Microsoft.EntityFrameworkCore.SqlServer.NetTopologySuite Microsoft.EntityFrameworkCore.InMemory There are the packages for Postgres and SqlLite:Microsoft.EntityFrameworkCore.Sqlite.NetTopologySuite Npgsql.EntityFrameworkCore.PostgreSQL.NetTopologySuite Then you need to include in your DbContext:optionsBuilder. UseSqlServer(@"Data Source=(localdb)\MSSQLLocalDB;Initial Catalog=WideWorldImporters", x => x.UseNetTopologySuite()); For a complete explanation here you have here in the official documentation: https://docs.microsoft.com/pt-br/ef/core/modeling/spatial

Just use Remove-Migration He'll get the latest Add-Migrationbefore performing Update-Database If you have already used Update-Database It will be necessary to remake changes create a new Add-Migration and then rotate Update-Database Friso again that the Remove-Migration only works when it has not yet been realized Update-Database

Good morning, buddy.I've been giving a thought and the way I found was to make a property that will store these changes and a method to record this information in Set of each property.public partial class MinhaClasseExemplo { public int Id { get { return this.Id; } set { GravaLogPropAlterada(Id); this.Id = value; } } public List<string> PropriedadesAlteradas { get; private set; } = new List<string>(); public void GravaLogPropAlterada(object property) { PropriedadesAlteradas.Add((InfoOf(() => property).ToString())); } static PropertyInfo InfoOf<T>(Expression<Func<T>> ex) { return (PropertyInfo)((MemberExpression)ex.Body).Member; } }That would be the idea.I hope I gave you a light!

Galera manage to solve where I used to add cookie only put encodeURIComponentdocument.cookie = 'Nome=' + encodeURIComponent((JSON.stringify(produtos))); and for reading decodeURIComponentI take the cookie by name after use 'decodeURIComponent':var cookieValue = document.cookie.replace(/(?:(?:^|.*;\s*)Nome\s*\=\s*([^;]*).*$)|^.*$/, "$1"); var dec = decodeURIComponent(cookieValue);

To solve this question I had to make a change in the bank. Obervation: The change in coding in the bank, table and columns. How can be seen in the code below ALTER DATABASE `banco` CHARACTER SET utf8 COLLATE utf8_unicode_ci; ALTER TABLE `banco`.`tabela` CHARACTER SET utf8 COLLATE utf8_unicode_ci; ALTER TABLE `banco`.`tabela` MODIFY `Coluna` varchar(100) CHARACTER SET utf8 COLLATE utf8_unicode_ci;

What do you have to do in these cases, in the API you get the ID of the object you want to update right? Then you would have to do the following steps, I will create a scenario here.This is your model (example):class Pessoa{ public int Id { get; set; } public string Nome { get; set; } public string Email { get; set; } } Ai in the API you receive (JSON) to update only the name:{ "Id" : 1, "Nome" : "Atualização" } you will have to do the following action, search in the bank the object referring to this ID:var pessoa = contexto.Pessoa.First(x => x.Id == model.Id); update only the field you want in this request (this ensures that if the model name property that came via JSON is null, keep the previous value):pessoa.Nome = model.Nome ?? pessoa.Nome; is then and only save in the database:contexto.SalveChanges(); If you place null values on the object that will be saved the EF-Core cannot identify that you should not (try) record this record in the bank, the validation if the field is null or not and a "business rule" and has to be validated before the SaveChanges() what EF-Core does and put NOT NULL prevented recording, if this is configured in creating the database.

If you want instances to be created automatically, you need to register any and all dependency on them. This includes registering an instance of AEContext to be injected into what you call Repository.Btw, I'm not sure if you want the instance to be by scope or transient, I used the method AddScoped based on the existing code.So we lack to do this in the method ConfigureServicespublic void ConfigureServices(IServiceCollection services) { //... services.AddScoped<AEContext>(); }

Having the conversions explicit, just do the following://Convertendo B para A List<B> listB = listA.Select(a => (B)a).ToList(); //Convertendo A para B List<A> listA = listB.Select(b => (A)b).ToList(); With the example above I'm assuming you have the classes A and B:public class A { public int Id { get; set; } public string Role { get; set; } public string Email { get; set; } public static explicit operator A(B b) { return new A { Id = b.id_b, Role = b.prop_b1, Email = b.prop_b2 }; } } public class B { public int id_b { get; set; } public string prop_b1 { get; set; } public string prop_b2 { get; set; } public static explicit operator B(A a) { return new B { id_b = a.Id, prop_b1 = a.Role, prop_b2 = a.Email }; } } https://dotnetfiddle.net/XlTmaK

Cpf_Cpnj should be Cpf_Cnpj in the following line: Cpf_Cnpj = dt.Rows[i]["Cpf_Cpnj"].ToString(), // Problema ocorre nesta linha

If you are using Identity just do it like this:In View@using Microsoft.AspNetCore.Identity; @inject SignInManager<ApplicationUser> SignInManager @inject UserManager<ApplicationUser> UserManager //DIV onde vai aparecer o nome do usuário logado <div>@UserManager.GetUserName(User)</div> //OU <div>@User.Identity.Name</div>

What you can do is instead of using Id as int you can use the GUID that will always give you a string sequence. Id = Guid.NewGuid(); This way you will always have a unique identifier and will know which one it is before registering in the bank.

You can use the type Byte[], https://docs.microsoft.com/pt-br/ef/ef6/modeling/code-first/data-annotations#timestamp .[Timestamp] public Byte[] CreatedAt { get; set; } Defining the type of your field as Byte[] and using the attribute [Timestamp] it will be recorded with https://docs.microsoft.com/en-us/sql/t-sql/data-types/rowversion-transact-sql?view=sql-server-2017 .timestamp is synonymous with the type of rowversion data and is subject to behavior of data type synonyms. In DDL instructions, use rowversion instead of timestamp whenever possible. To get more information, see Synonyms of data type (Transact-SQL).Updating the database with the parameter -Verbose you will have the following SQL to generate the table (change only your field CreatedAt as I showed above):CREATE TABLE [dbo].[UserBaseEntities] ( [Id] [int] NOT NULL IDENTITY, [CreatedAt] rowversion NOT NULL, [UpdatedAt] [varbinary](max), CONSTRAINT [PK_dbo.UserBaseEntities] PRIMARY KEY ([Id]) )

You can send everything in one object only.There's a lot of discussion about it when you're creating https://pt.stackoverflow.com/questions/45783/o-que-%C3%A9-rest-e-restful . For it is convention that each object must have its own Controller and that POST methods receive only one object.But this always goes according to the needs of the programmer/software.If you're sending everything at once, you can ride and send JSON this way for example:var Quiz = { nome: "Quiz 01", perguntas: [ { nome: "Pergunta01", respostas: [ { nome: "resposta A" }, { nome: "resposta B" } ] }, { nome: "Pergunta 02", respostas: [ { nome: "resposta A" }, { nome: "resposta B" } ] } ] } I hope I helped.

The problem occurs because by default the IHttpContextAccessor no longer connected.To solve this problem we must manually connect/register the service within the class Startup.cspublic void ConfigureServices(IServiceCollection services) { services.Configure<CookiePolicyOptions>(options => { // This lambda determines whether user consent for non-essential cookies is needed for a given request. options.CheckConsentNeeded = context => true; options.MinimumSameSitePolicy = SameSiteMode.None; }); services.AddSingleton&lt;IHttpContextAccessor, HttpContextAccessor&gt;(); // Adicione eessa linha para que seu projeto volte a funcionar normalmente. services.AddSession(); services.AddMvc().SetCompatibilityVersion(CompatibilityVersion.Version_2_1); }