In ASP.NET MVC, we manipulate Views, among other things. Some of these Views represent full pages and some are just page parts. These parts or areas belonging to a view are called partial views, and they are also returned by controller actions. Since these partial views should only be used within a view, the ASP.NET MVC framework allows us to protect any call to these partial actions by decorating them with the ChildActionOnly attribute. This attribute makes sure that the action: - cannot be used as an entire view and the application developers will always run it using the HtmHelper.Action or HtmlHelper.RenderAction methods. - has a URL that will not be accessible via the address bar, if a user somehow becomes aware of the existence of this URL. However, as with any dynamic site, we will have AJAX requests that can also make requests for HTML content without having to load the page completely. This content also represents a part, and when we receive the response from the web server we have to embed this piece of HTML somewhere in the page. The AJAX request sent to the server will certainly invoke a controller action. This action, like those marked with the ChildActionOnly attribute, must have these constraints: - should only go through AJAX requests. - inaccessible via the browser address bar. But the ASP.NET MVC framework does not offer any attributes that allow us to apply these restrictions to an action, but it gives us the tools to create them....

Kürzlich habe ich eine Frage auf der StackOverflow Webseite beantwortet. Die Situaton war wie folgt. ...

I recently answered a question that came up on the StackOverflow website. The question was whether using the ViewBag dynamic property of the controller to expose the error message was a good practice, as the OP investigations suggested that it was necessary to expose properties from the model. Obviously it is highly recommended NOT to use the ViewBag property since it does not provide any Strong Typing. If you want to communicate with the view you should always involve a typed model. The suggested solution is therefore legitimate in that respect, however, it is not a good practice when it comes to model error handling in ASP.NET MVC. The solution for exposing error messages (as in the previous example, which does not use data annotation attributes) derives from the use of the AddModelError method, from the ModelStateDictionary class. We do not need to instantiate this class because a ModelState property containing an instance of this class already exists in the Controller. Therefore, the right solution is the following:...

Microsof bietet eine Vielzahl von Zertfzierungsprogrammen an, die dir bei der Entwicklung deiner Fäh...

Microsoft offers a wide range of online certification programs designed to help you grow your skills and your career. This article will focus on developer certifications....

Ich begann zu programmieren, als ich in der High School war. Ich habe in den letzten zehn Jahren einige Lektionen gelernt und dachte, ich würde mir einen Moment Zeit nehmen, um meine Gedanken zu diesen Themen zu sammeln....

I started programming when I was in high school. I learned a few lessons over the past decade, and I thought I would take a moment to gather my thoughts on these things. It took me about ten years and a lot of experimentation to figure out some of this....

If you don't know what Xamarin is, may I suggest that you start by reading my introductory notes before proceeding with this ? For those in the now, let's get into it without further ado....

Wenn du nicht weißt, was Xamarin ist, schlage ich vor, dass du zuerst meinen Einführungsartkel liest...

Just Keep Moving Forward....