Difference between ASP.NET web application and ASP.NET website

When we create web projects with ASP.NET we can either choose Web Application or Web Site. Both of these project types function and perform similarly, but they differ in many important ways which may impact are decision while creating the projects. Few of the differences are as follows:

Reference - MCTS self-paced training kit (Exam - 70-515)

1. You can create an MVC application.

2. Visual Studio stores the list of files in a project file (.csproj or .vbproj), rather than relying on the folder structure.

3. You cannot mix Visual Basic and C#. This is because files are stored .csproj or.vbproj and we have only one proj file.

4. You cannot edit code without stopping a debugging session.

5. You can establish dependencies between multiple web projects.

6. You must compile the application before deployment, which prevents you from testing a page if another page will not compile. In website projects all the pages are complied independent of each other.

7. You do not have to store the source code on the server.

8. You can control the assembly name and version.

9. You cannot edit individual files after deployment without recompiling.

Comments

Laravel XAMPP MySQL artisan migrate install error mysql.sock

In my previous post I wrote about setting up Laravel 4 on Mac with XAMPP . When I tried to use migrations (using artisan) I faced some issue. I will also post about Laravel migrations soon. php artisan migrate:install Error : [PDOException] SQLSTATE[HY000] [2002] No such file or directory Solution : We need to tell artisan which mysql we want it to use. For this to work we need to porivde it with mysql.sock which we want it to use. So change your database settings like this: 'mysql' => array( 'driver' => 'mysql', 'host' => 'localhost', 'unix_socket' => '/Applications/xampp/xamppfiles/var/mysql/mysql.sock', 'database' => 'wedding', 'username' => 'root', 'password' => '', '

Add (Drop) a new article (table) at publisher in merge replication

Let us add the article using the GUI first. First of all create the table on publisher database. Now right click on the publisher and select properties from the menu. Click on articles. Uncheck the - "Show only checked articles in the list" checkbox, in order to see the newly added table. Select the table as shown in the figure below. Press ok The article has now been added to the publisher We now need to recreate the snapshot Right click the publication and select – “View snapshot agent status”. Click start to regenerate snapshot. Now right click on the subscription (I have both on same server you may have on different servers) and select “View synchronization status” Click on start on the agent. The schema changes will propagate to the client if you have "Replicate schema changes" property set to true in the publisher.

Check SQL Server Job status (State) using sp_help_job and xp_sqlagent_enum_jobs

This article is about checking the status of a SQL job. In our work place we have lot of SQL jobs. These jobs will run whole day and are business critical. They will load the data and generate extracts which will be used by business people. Thus, it becomes quite essential to support the system efficiently so that the job finishes in time and as desired. Also, while designing a new system sometimes we need to check the dependency of one job over another. In such scenario we need to check whether a particular job has finished or not. All this can be achieved in SQL Server by using the procedures:- sp_help_job xp_sqlagent_enum_jobs Note: xp_sqlagent_enum_jobs is an undocumented proc inside of sp_help_job and is used extensively to get SQL agent job information. sp_help_job: This procedure gives some insight into the status, and information, about a job. This stored procedure provides information such as last start time, job status etc. Syntax sp_help_job { [ @job_id= ] jo

Anuj's Share IT

Search This Blog