All posts by crbtech

How To Deploy ASP.NET Core to IIS

To deploy an ASP.NET Core app to IIS isn’t that difficult, but hosting in ASP.NET Core is a little different than ASP.NET.

Deploy_ASP_DOT_NET_Core_to_IIS

Lets Configure an ASP.NET Core App For IIS

To mention about ASP.NET Core project is that they are console applications. Your project has a Program.cs file like a console app would have and it has the following code:

public class Program

{

public static void Main(string[] args)

{

var host = new WebHostBuilder()

.UseKestrel()

.UseContentRoot(Directory.GetCurrentDirectory())

.UseIISIntegration()

.UseStartup()

.Build();

host.Run();

}

}

What do you mean by WebHostBuilder?

All ASP.NET Core applications need a WebHost object that serves as an application and web server. WebHostBuilder is used to configure and develop WebHost. You can see UseKestrel() and UseIISIntegration() in the WebHostBuilder setup code.

What do they do?

UseKestrel() – This registers IServer interface for Kestrel that will be used to host your application. In the future, there would be other options, which include WebListener and that would be Windows only.

UseIISIntegration() – This says to ASP.NET that IIS will work as a reverse proxy in front of Kestrel. This then specifies some settings around which port Kestrel must listen on, forward headers, and other details.

If you are planning to deploy your application to IIS, UseIISIntegration() is needed.

What is AspNetCoreModule?

An ASP.NET Core projects create a web.config file. This is used to deploy your application to IIS. It registers AspNetCoreModule as an HTTP handler.

Default web.config for ASP.NET Core:

<?xml version=”1.0″ encoding=”utf-8″?>

<configuration>

<system.webServer>

<handlers>

<add name=”aspNetCore” path=”*” verb=”*” modules=”AspNetCoreModule” resourceType=”Unspecified”/>

</handlers>

<aspNetCore processPath=”%LAUNCHER_PATH%” arguments=”%LAUNCHER_ARGS%” stdoutLogEnabled=”false” stdoutLogFile=”.\logs\stdout” forwardWindowsAuthToken=”false”/>

</system.webServer>

</configuration>

AspNetCoreModule manages all incoming traffic to IIS and acts as reverse proxy that knows how to forward the traffic to your ASP.NET Core application.

Install .NET Core Windows Server Hosting Bundle

Before you start deploying your application, you must install the .NET Core hosting bundle for IIS. This will install .NET Core runtime, libraries, and ASP.NET Core module for IIS.

After doing that, you might need to do a “net stop was /y” and “net start w3svc” to make sure all the changes are taken for IIS.

Steps to Deploy ASP.NET Core to IIS

You have to configure WebHostBuilder to use Kestrel and IIS. Your web.config must exist and look similar to the example above.

Step 1: Publish to File Folder

Publish to a Folder with VS 2017

Step 2: Copy Files to Preferred IIS Location

Copy the published files where you want them live. If you deploy to a remote server, you might need to zip the files and move to the server. If you intend to deploy to a local dev box, you can copy them locally.

Step 3: Create Application in IIS

Firstly, make a new IIS Application Pool. You might like to develop one under the .NET CLR version of “No Managed Code“. Remember IIS works as a reverse proxy, it doesn’t execute any .NET code.

Next, develop your new application under your existing IIS Site, or design a new IIS site.

Step 4: Load Your App

Your application must load well. If it doesn’t, check the output logging from it. Within your web.config file, you explain how IIS starts up your ASP.NET Core process. Get output logging done by setting stdoutLogEnabled=true and you might also want to change the log output location as configured in stdout log file.

Advantages

Microsoft suggests using IIS with any public facing site for ASP.NET core hosting. IIS gives additional levels of configuration, security, management, logging, and several other things.

One of the biggest advantages of using IIS is process management. IIS will start your app automatically and restart it if a crash has to occur.

Now with this, we conclude. We hope this was of help to you.

Keep coding!!

If you want to enhance yourself in Dot Net Course and improve yourself through Dot NET training program then our institute CRB Tech Solutions would be of great help and support. We offer a well-structured program for the best Dot Net Course. Among many reputed institutes of dot net training and placement in Pune.

Stay connected to with us for your technical up-gradation and to remain updated with all the happenings in the world of Dot Net.

Don't be shellfish...Buffer this pageEmail this to someoneDigg thisShare on FacebookShare on Google+Share on LinkedInPrint this pageShare on RedditPin on PinterestShare on StumbleUponTweet about this on TwitterShare on Tumblr

Ways To Configure log4net For .NET Core

We start with the mention that the log4net team published new NuGet packages which support.NETStandard 1.3, which says it must work with .NET Core. This article is to discuss updates for log4net support.

Ways To Configure log4net For Dot NET Core

To start with: Configure() log4net

To add a reference to the log4net NuGet package is no problem. If you worked previously with log4net for any amount of time, you know that you must add codes for configuring it.

XmlConfigurator.Configure() needs some parameters that we didn’t usually provide in the past.

Configuration Workaround: Load It Manually

This log4net is good enough to load its configuration from a web.config or log4net.config file. In .NET Core, it doesn’t appear to know how.

It makes sense that this can’t read from a web.config/app.config because they don’t exist in .NET Core.

But, it doesn’t automatically try to read a log4net.config file. To mention, NLog does the same thing. You need to configure manually as in .NET Core.

With little little reverse dtudying, you will know how to load the log4net.config file and configure log4net.

var logRepository = LogManager.GetRepository(Assembly.GetEntryAssembly());

XmlConfigurator.Configure(logRepository, new FileInfo(“log4net.config”));

You can get this to work with a .NET Core app targeting both netcoreapp1.0 and net452. Sum up that to your Program.cs as the first thing your code does.

There is a mention about some limitations with the current 2.0.7 version of log4net. Hopefully, there will be some more developments.

Now with this, we conclude. We hope this was of help to you.

If you want to enhance yourself in Dot Net Course and improve yourself then our institute, CRB Tech Solutions would be of great help and support.

They offer a well-structured program for the best Dot Net Training course. Among many reputed institutes of dot net training and placement in Pune. Keep coding!!

Don't be shellfish...Buffer this pageEmail this to someoneDigg thisShare on FacebookShare on Google+Share on LinkedInPrint this pageShare on RedditPin on PinterestShare on StumbleUponTweet about this on TwitterShare on Tumblr

Things To Know About Changes In Dot NET Core 2.0

Technology keeps on updating and the best dot net tips are to remain upgraded with time and pace. Here we list the changes in .Net Core 2.0.

Things_To_Know_About_Changes_In_Dot_NET_Core_2_0

1] .NET Standard 2.0 Extended APIs & the Potential to Reference Full Framework Libraries

.NET Standard expands the set of available APIs to include several missing features. It now supports over 32,000 APIs. It is now easier to connect your code to a .NET Standard library without major changes in code.

One of the biggest issues with .NET Core was the absence of third party libraries. For instance, when 1.0 was released, the logging libraries like log4net were not available, but now it is.

But that was a problem if you wanted to deploy your app on Mac or Linux. You could have made use of .NET Core and targeted full .NET framework to avoid these issues.

.NET Standard 2.0 has summed up a new compatibility shim that enables any .NET Core app to reference any library of the full framework.

2] Detailed OS Support

One of the big successes with .NET Core is to be able to port across multiple operating systems that include desktops, servers, and even mobile. Microsoft and the community continue to amplify the support of .NET Core.

Linux is considered as a single operating system instead of different distributions. This is also true for Windows and macOS.

3] ASP.NET Core Razor Pages Are Something New

ASP.NET presently supports razor syntax based pages, called Razor Pages. You can now develop a razor view without a controller. Though, you can make a class that takes in from PageModel which is actually a controller and model class for that page

4] This Has AVisual Basic for .NET Core!

It’s news that Visual Beginners All-purpose Symbolic Instruction Code supports .NET Core. Though it is limited to developing class libraries and console application, more is coming sooner.

If you have missed the changes in .NET 1.1, here we bring you some highlights.

1) xproj Project Files substituted by New Version of csproj

One of the main differences with .NET Core was new project files. Visual Studio used xproj and project.json files instead of the conventional csproj. The format of new project file was very simple but didn’t work with some .NET tools like msbuild.

2) MSBuild Now Works

3) Visual Studio 2017 – Enhancements to Tools

When project.json is not there, then how to perform multi-targeting of frameworks and the VS UI around references and dependencies completely changed in VS 2017.

To perform multi targeting, you have to edit the csproj file manually and things can turn little weird. The fact is that if you are targeting one framework, you can do it within the project properties.

To mention, one big advantage of VS 2017 is its easiness to install.

To be successful in yours .Net career, try to enhance your skill set in Dot Net Course and improve yourself through Dot NET training programs. In this reference, CRB Tech Solutions, Pune could be of great help and support for you.

They offer an industry oriented program for the best Dot Net courseStay connected to this space for more technical blogs and updates related to the world of Dot Net.

Keep coding!!

Don't be shellfish...Buffer this pageEmail this to someoneDigg thisShare on FacebookShare on Google+Share on LinkedInPrint this pageShare on RedditPin on PinterestShare on StumbleUponTweet about this on TwitterShare on Tumblr

Tips To Increase Visual Studio Editor Window Space Rapidly

Today under the topic for dot net coding tips and tricks, we shall discuss how to maximise the Visual Studio window space faster.

Tips To Increase Visual Studio Editor Window Space Rapidly

 

Many of you must like to prefer that, right? To bestow more screen space in Visual Studio to the editor window as possible.

At times doing the same on full-screen mode might not be that easy or your requirement, because getting to several tool windows — Solution Explorer, for example — isn’t certain.

Here we share Dot Net tips to bring back the tool panes to the windows layout, after hiding them by one click.

If you want to get the maximum space for your editor’s window without giving up the VS window, then go to Windows menu and select the option, Auto Hide All. That choice will collapse all of your tool panes: Solution Explorer, the Properties List, the toolbox, and all the related things will collapse into the sides of the Visual Studio, providing you a maximum editing space inside the Visual Studio.

You can definitely bring back the tool panes when you need them by a single click, but there is no “auto un-hide all” option; so you have to bring back every tool pane, individually.

In Visual Studio 2015, there was an alternative to bring back each tool page one-by-one. To make use of this, you need to first set up your “preferred” layout of tool panes. Next, assign this Windows layout a name and save it by visiting the Window menu and by selecting Save Window Layout.

With your preferred, saved the layout, after applying Auto Hide All; you can go back to the tool panes of your choice by selecting Window | Apply Window Layout | <your layout name> from the menu drop down list.

To mention, the earlier versions of Visual Studio did not have any option to save Windows layouts but only kept in memory, the layouts for 4 fixed modes: Design, Debug, Full Screen, and File.

Now with this, we conclude our today’s blog under dot net tips and tricks. We hope this was of help to you.

Keep coding!!

To be successful in yours .Net career, try to enhance your skill set in Dot Net Course and improve yourself through Dot NET training programs. In this reference our institute i.e. CRB Tech Solutions Pune could be of great help and support for you.

Stay connected to this space for more technical blogs and updates related to the world of Dot Net.

Don't be shellfish...Buffer this pageEmail this to someoneDigg thisShare on FacebookShare on Google+Share on LinkedInPrint this pageShare on RedditPin on PinterestShare on StumbleUponTweet about this on TwitterShare on Tumblr

Why You Need To Add An Error Handler To Your ASP.NET MVC Controller

Today we shall discuss error handling under the topic of dot net tips and tricks.

Need_To_Add_An_Error_Handler_To_Your_ASP_DOT_NET_MVC_Controller

An error handler is significant in order to avoid future problems. There isn’t anything like an “unhandled error” — if your code causes an error outside of a Try…Catch block, then the error will come up through several ASP.NET and .NET Framework error handlers. An “unhandled error” is actually another form of an error that you couldn’t handle.

Here we share Dot Net tips to avoid an error from bubbling up in future.

In ASP.NET MVC you could handle lots of errors by inserting an error handler inside your Controller: You need to add a OnException method to your Controller. The code will be implored each time there is an “unhandled error” in the Controller.

It’s an easy way to add the method: In your Controller, you need to type Overrides (in Visual Basic) or override (in C#), next press the Tab key to get a list of override methods, pick OnException from the drop down list, and again press the Tab key. Visual Studio will write the structure of the method for you.

The version for Visual Basic will as shown below:

Protected Overrides Sub OnException(filter context As ExceptionContext)

End Sub

Your method then sends an ExceptionContext object whose Exception property will give you access to all of the information telling what went wrong. Within the OnException method, you can do anything you want about the error which appears specific to the Controller. If you don’t take any further action, the error will keep coming up to the ASP.NET error handler.

And if you are willing to finish by making use of RedirectToRouteResult method built into the Controller to send the user an error page of your choice then you must stop that process, by which the error pops out. You can do with this line:

filter context.ExceptionHandled = True

This sets the ExceptionContext object’s ExceptionHandled property to True.

Now with this, we conclude. We hope this was of help to you. Keep looking into this space for more blogs on dot net coding tips and tricks.

Keep coding!! 

To be successful in yours .Net career, try to enhance your skill set and improve yourself through Dot NET training programs. In this reference, CRB Tech Solutions, Pune could be of great help and support for you.

Stay connected to this space for more technical blogs and updates related to the world of Dot Net.

Don't be shellfish...Buffer this pageEmail this to someoneDigg thisShare on FacebookShare on Google+Share on LinkedInPrint this pageShare on RedditPin on PinterestShare on StumbleUponTweet about this on TwitterShare on Tumblr

How To Introduce NuGet Packages With .NET Core On RHEL

NuGet is an open source manager of packages for the .NET Core system. Those who are familiar with Red Hat Enterprise Linux or RHEL, it’s great for pulling libraries into .NET Core project.

Introduce NuGet Packages With Dot NET Core On RHEL

Repositories

Very much like the RHEL, NuGet has its own storage system to get packages. By default, with the installation of .NET Core runtime, the nuget.org repository gets added to your system. You can see this by seeing ~/.nuget/NuGet/NuGet.Config.

<?xml version=”1.0″ encoding=”utf-8″?>

<configuration>

<packageSources>

<add key=”nuget.org” value=”https://api.nuget.org/v3/index.json” protocolVersion=”3″ />

</packageSources>

</configuration>

More information on different NuGet.Config files and their application can be found in Microsoft’s documentation for Configuring NuGet Behaviour.

Finding a package

You can find different places for the packages. Which one you use depends on the information you know about the package.

If you know the package’s name and want to know the current version or targets which framework version, you can take help of the nuget.org to search.

Sometimes you might know a name of a class or method. Then the nuget.org search won’t work that well here, so MS created a Reverse Package Search tool. There you could enter any class or method name, and the search results will get linked to the project on nuget.org.

You should know that any developer can design an account and upload packages to NuGet. This says that the packages must be screened before using in a production system. You can trust a package if it has a high download count and the package shows active development. If in doubt, it’s better to visit the existing home page of the project.

How to add packages to your project?

There are two ways for the same:

Using the .net add command

Manual modification of .csproj file

Using .net adds is the easiest because it automatically runs a package restore and download the package.

Local packages

If you want to develop your own library for use across multiple projects, you’ll definitely want to reference those libraries. As NuGet is the only way to add references to a .NET Core project, you have two options:

You can develop an account and upload your package to nuget.org.

You can host an internal NuGet storing space.

During the writing this blog, there has been no NuGet hosting software which runs on Linux. The only option is that you have to use a directory to hold your NuGet packages. To mention, this could be a directory on your local machine or a networked file share. Below the mention is about local directory.

First, design a directory for your packages. This could be anywhere your user has access.

This post doesn’t focus on how to create a NuGet package, but you copy them on a directory you created. Next you have to tell .NET about this directory. In your project folder, develop a new NuGet.Config with the following content.

<?xml version=”1.0″ encoding=”utf-8″?>

<configuration>

<packageSources>

<add key=”mynuget” value=”/usr/share/nuget” />

</packageSources>

</configuration>

Next add a package to your project making use of your chosen method.

Now with this, we conclude. We hope this was of help to you.

Keep coding!!

If you want to enhance yourself in Dot Net Course and improve yourself through Dot NET training program; our institute would be of great help and support. Among many reputed institutes of dot net training and placement in Pune, CRB Tech has created a niche for itself.

Stay connected with us for your technical up-gradation and to remain updated with all the happenings in the world of Dot Net.

Don't be shellfish...Buffer this pageEmail this to someoneDigg thisShare on FacebookShare on Google+Share on LinkedInPrint this pageShare on RedditPin on PinterestShare on StumbleUponTweet about this on TwitterShare on Tumblr

Final Features Of .NET Standard 2.0

The .NET Standard is a specification of the entire API’s that a .NET platform needs to implement in order to form a .NET platform. The standard is an open source, and you can find every different version and API’s in the same place.

Final Features Of .NET Standard 2.0

Now the .NET Standard 2.0 is with its final look. Microsoft has announced this and said that users can create .NET Standard 2.0 libraries and NuGet packages as well, but the company has suggested making use of .NET Core Preview 2 as it has several necessary enhancements to make your experience better.

Extra ordinary features of .NET Standard 2.0 as suggested by Microsoft:

Bigger API Surface

With doubled set of available APIs from 13k in .NET Standard 1.6 to 32k in version 2.0. will make it easier to port current codes to .NET Standard, and also to any .NET implementation of .NET Standard, like .NET Core 2.0 and the next version of UWP.

.NET Framework mode of compatibility

Majority of NuGet packages targets .NET Framework. Many projects are being blocked at present from moving to .NET Standard because all their dependencies are not targeting .NET Standard. Hence the need of compatibility mode that permits .NET Standard projects to depend on libraries of .NET Framework as if they were made for .NET Standard. It has been found that about 70% of NuGet packages on nuget.org are API compatible with .NET Standard 2.0, hence practically, it unblocks several projects.

Broad platform support

This will be supported on the below mentioned platforms:

.NET Framework 4.6.1

.NET Core 2.0

Mono 5.4

Xamarin.iOS 10.14

Xamarin.Mac 3.8

Xamarin.Android 7.5

Besides this, the company also told about the prerequisite tools for using .NET Standard 2.0. You need the latest versions of the following tools :

.NET Core SDK : Microsoft recommended to install .NET Core 2.0 Preview 2. This includes CLI as well.

Visual Studio: Users For this, you have to install Visual Studio 2017 15.3 which is the latest version of VS. For Mac users, the latest version of Visual Studio for Mac is perfect.

For more details, you can visit Microsoft site or read their release documents.

Now with this, we conclude. We hope this was of help to you.

Keep coding!! If you want to enhance yourself in Dot Net Course and improve yourself through Dot NET training program; our institute would be of great help and support. We offer well structured program for the Best Dot Net Training Course. Among many reputed institutes of dot net training and placement in Pune, CRB Tech has created a niche for itself.

Stay connected with us for your technical up-gradation and to remain updated with all the happenings in the world of Dot Net.

Don't be shellfish...Buffer this pageEmail this to someoneDigg thisShare on FacebookShare on Google+Share on LinkedInPrint this pageShare on RedditPin on PinterestShare on StumbleUponTweet about this on TwitterShare on Tumblr

3 Aspects Every ASP.Net Developers Must Know

With several options to design web applications in MS ecosystem like ASP.Net MVC, ASP.Net Web Forms, Single Page Applications. From the start of ASP.Net it supported ASP.Net Web Forms and even today enterprises develop many of web applications using them. The web forms help you create faster web applications.

3 Aspects Every ASP.Net Developers Must Know

But it envelops the underlying technology i.e. HTTP totally.

If you know the basics, you must know how to summon javascript from your code behind codes in ASP.Net Code.

In this article, we covered 3 basic things which every ASP.Net developer must know while using ASP.Net Web Forms

1.The nature of HTTP and Request-Response pattern:

All web applications are created using ASP.Net use HTTP protocol or its secured versions. You can consider HTTPS as using HHTP safely. HTTPS makes use of Secure Socket Layer (SSL) and encrypts your data. But, HTTPS still use HTTP.

HTTP is a no state protocol which follows a response/request pattern i.e., the user requests a resource and the web server sends the resource.

The web server never keeps any state of the previous requests. If the user requests for the same resource, the web server will respond as if the request was made for the first time. There are several ways to maintain the state in a web application. ViewState is one such way. Here all the data is coded in a hidden field and sent to the client and hence the state can be maintained between requests.

There are several other ways available to maintain the state which would be discussed later. For the time being, it is for your information that even though HTTP is stateless, there are certain options to maintain the state.

2. Role of CSS, HTML,Javascript, ASPX page in ASP.Net web application

Your browser can only understand HTML, CSS, javascript . So the web technology must be converted to technology based code to HTML, CSS and JS.

HTML provides the layout of the web page.

CSS or Cascading style sheet will help you in putting styles to elements on the page.

Javascript is to process the elements at client side without hitting the server. Javascript is used only for validation, to handle the user input, to change the style of some element based on data or user input etc…

When a user reaches out for the ASP.Net web page, these are the sequence of events that occur:

User reaches out the web page

The request is sent to the server where the web application is hosted. The web server carries forward the request to ASP.Net because the requested resource is of aspx page.

Net converts ASP.Net code into CSS, HTML and JS

The changed document is sent back to the user and the user gets the web page via the browser.

3. Differences between client side and server side

The ASP.Net server controls are changed into HTML elements at server side and the changed HTML parts are sent to the browser. To mention, javascript works only on HTML parts, and you must know the HTML element of ASP.Net server control that you are making use of to have the attributes changed.

Now we conclude. Keep coding!!

If you want to enhance yourself in Dot Net Course and improve yourself through Dot NET training program; our institute CRB Tech Solutions would be of great help and support. We offer well structured program for the Best Dot Net Training course.

Stay connected to with us for your technical up-gradation and to remain updated with all the happenings in the world of .Net.

Continue reading

Don't be shellfish...Buffer this pageEmail this to someoneDigg thisShare on FacebookShare on Google+Share on LinkedInPrint this pageShare on RedditPin on PinterestShare on StumbleUponTweet about this on TwitterShare on Tumblr

The Use Of Validation Groups Inside ASP.NET User Controls

What does Validation groups do? Well, they permit you to validate data entry controls in the groups. Server controls like validation controls, Button and TextBox have ValidationGroup attributes that have a string value.

The Use Of Validation Groups Inside ASP.NET User Controls

All the server controls which have the same ValidationGroup value acts as a single validation group. Validation groups are necessary when you want to analyze only a small set of controls from several controls housed on a Web Form. Using validation groups is very easy and straight. But if you have a validation group inside a user control and there are many control instances on a Web Form you come across some problems.

To understand in details let’s develop a simple user control.

The Web Form has two instances of a user control – TestUC.ascx. The user control has a TextBox, a RequiredFieldValidator and a Button. The codes of the user control is shared below:

<asp:TextBox ID=”TextBox1″ runat=”server”></asp:TextBox>

<asp:RequiredFieldValidator ID=”RequiredFieldValidator1″ runat=”server”

ControlToValidate=”TextBox1″ ErrorMessage=”*” Font-Bold=”True”

Font-Size=”30px” ForeColor=”Red”>*</asp:RequiredFieldValidator>

<asp:Button ID=”Button1″ runat=”server” OnClick=”Button1_Click” Text=”Submit” />

<br />

<br />

<asp:Label ID=”Label1″ runat=”server” Font-Bold=”True” ForeColor=”Red”></asp:Label>

The Web Form has two instances of TestUC.ascx as mentioned below:

<%@ Page Language=”C#” … %>

<%@ Register Src=”~/TestUC.ascx” TagPrefix=”uc1″ TagName=”TestUC” %>

<!DOCTYPE html>

<html xmlns=”http://www.w3.org/1999/xhtml”>

<head runat=”server”>

<title></title>

</head>

<body>

<form id=”form1″ runat=”server”>

<uc1:TestUC runat=”server” id=”TestUC1″ />

<br />

<uc1:TestUC runat=”server” id=”TestUC2″ />

</form>

</body>

</html>

If you put the ValidationGroup property of TextBox1, RequiredFieldValidator1 and Button1 to some string (e.g. VG) and then carry out the Web Form you will find that once getting clicked either of the Submit buttons, both the RequiredFieldValidatior controls display an error.

This behavior though not expected but occurs as both the instances of the user control using same ValidationGroup value.

To remove this problem you can take two approaches:

Provide a different and unique ValidationGroup value to the user control from the Web Form

Produce a unique value for ValidationGroup inside the user control

The first solution needs creation of a property (e.g. ValidationGroup) in user control. This attribute will accept a unique string value for the ValidationGroup and will assign to all the other necessary server controls. This is how the property can be developed:

public string ValidationGroup

{

get

{

return Button1.ValidationGroup;

}

set

{

Button1.ValidationGroup = value;

TextBox1.ValidationGroup = value;

RequiredFieldValidator1.ValidationGroup = value;

}

}

As shown, the set block of ValidationGroup attribute assign the given value to the ValidationGroup of Button1, TextBox1 and RequiredFieldValidator1.Once the ValidationGroup property is developed you can set it from the Web Form as given below:

<form id=”form1″ runat=”server”>

<uc1:TestUC runat=”server” id=”TestUC1″ ValidationGroup=”Group1″ />

<br />

<uc1:TestUC runat=”server” id=”TestUC2″ ValidationGroup=”Group2″ />

</form>

The ValidationGroup property of TestUC1 and TestUC2 is set to different and unique values. Now each user controls will work as per expectations.

In the next approach mentioned above you can auto-generate ValidationGroup value within the user control itself. The following code tells you how:

protected void Page_Load(object sender, EventArgs e)

{

if(!IsPostBack)

{

string vgId = Guid.NewGuid().ToString();

Button1.ValidationGroup = vgId;

TextBox1.ValidationGroup = vgId;

RequiredFieldValidator1.ValidationGroup = vgId;

}

}

The above code reveals the Page_Load event handler of the user control. The Page_Load event handler develops a new Guid using Guid.NewGuid() method. Next it sets ValidationGroup property of Button1, TextBox1 and RequiredFieldValidaror1 to this Guid string. Thus, every example of user control gets a unique ValidationGroup value and the Web Form woks as expected.

That’s it for now! Keep coding!!

If you want to enhance yourself in Dot Net Course and improve yourself through Dot NET training program; our institute would be of great help and support. We offer well structured program for the Best Dot Net Course

Stay connected to CRB Tech for your technical up-gradation and to remain updated with all the happenings in the world of Dot Net.

Don't be shellfish...Buffer this pageEmail this to someoneDigg thisShare on FacebookShare on Google+Share on LinkedInPrint this pageShare on RedditPin on PinterestShare on StumbleUponTweet about this on TwitterShare on Tumblr

9 Things To Remember When You Develop A New ASP.NET Web Forms Application

Many developers desire or prefer ASP.NET MVC for their new web applications. But this might not be always possible and you might use Web Forms for your next projects. In such situations developers have a doubt about difficulties during a switch from Web Forms to MVC. If certain guidelines are followed while developing a Web Forms project later migrating to MVC would be hassle free.

9 Things To Remember When You Develop A New ASP.NET Web Forms Application

Here we listed top 9 recommendations in dealing with the similar situation:

1. Take Advantage Of Class Libraries Wherever Possible

Class Libraries are best for writing codes which are independent of any specific type of UI, because they contain mainly POCOs. If you isolate codes in class libraries then reuse during and after migration, it would be quite direct. Of course, you have to design these class libraries in an ordered manner rather than dumping them.

2. Avoid server control level UI properties

One common mistake by beginners is to set UI properties of the server controls. For instance, BackColor, ForeColor, Font-Name and so on. These properties are transformed into style features of the respective control tag. The best approach is to place all such styling information in CSS style sheets and then make use of ClassName property of the server controls to add a CSS class.

3. Use Web API

Web API was presented along with MVC but now it has become a part of ASP.NET framework and you can utilize Web API in Web Forms applications also.

4. Avoid specific features of Web Forms

Web Forms use several features which are specific to Web Forms. These features are not present in MVC. Attributes like Themes and Web Parts fall in this category. Don’t use these attributes for new projects because this will become difficult to migrate them to MVC projects owing to lack of equivalent sets of features.

5. Design forms to avoid ViewState

Many Web Forms developers develop their pages for data entry such that multiple tasks happen on a single page. This might need page ViewState enabled resulting in bulky forms. You must see if such tasks could be done separately into their own pages and try to avoid ViewState totally.

6. Create reusable UI through User Controls

Developers of Web Forms have two choices for creating reusable user interfaces: Web User Controls and Custom Server Controls. If you design Custom Server controls you provide a rich design interface but this control is not easily reusable in MVC.

7. Use standard HTML over server controls

Rich server controls are the best strength of Web Forms applications. Controls like GridView and ListView are very popular. While using the controls ensure the migration path difficulties because there is no straight equivalent in MVC. Though you can’t avoid using them totally try minimizing their use whenever possible.

8. Keep in mind MVC even for Web Forms applications

Web Forms are not designed with MVC design pattern in mind, but you can think in MVC terms as well. The separation of concern (SoC) as put by MVC can be done in Web Forms as well.

9. Learn and make use of Design Patterns and SOLID principles

Make an effort to learn SOLID design principles and commonly used Design Patterns such that you can make your Web Forms applications in a good way.

That’s for now! Keep coding!!

If you want to enhance yourself in Dot Net Course and improve yourself through Dot NET training program; our institute CRB Tech Solutions would be of great help and support.

Stay connected for getting technical up-gradation and to remain updated with all the happenings in the world of .Net.

Don't be shellfish...Buffer this pageEmail this to someoneDigg thisShare on FacebookShare on Google+Share on LinkedInPrint this pageShare on RedditPin on PinterestShare on StumbleUponTweet about this on TwitterShare on Tumblr