Assign a static port to Website

by Vahid 15. December 2009 08:04
A while ago in a project we had the requirement to assign a static port number to our website project. The very first thing came to my mind was that we just can assign static port number to web application project type and we cannot assign a static port to web site project. Anyway I started searching in the internet for a solution to make sure about it. I spent quit a long time looking for an answer but I could not find any almost everywhere it was mentioned that we cannot assign a static port to a website and it is constrained to use dynamic port.I was convinced at the time and we managed to convert to web application. Surprisingly recently a friend of mine, Ali, referred a perfect solution for this issue to me and I thought it’s worth sharing with you. Step 1- the very first step is to add the Web Server external tool to Visual Studio. To do so
  • go to the Tool menu
  • Click on the External Tool menu


Step 2- next step is to actually adding the external tool. Once the external tool window is open, click on Add button and
  • In the title text box give your web server a name (in this case I have called it webserver 1919).
  • In the command text box enter your .net web server address (in my computer it is C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\WebDev.WebServer.EXE)
  • In the Arguments text box enter /port:{port number} /path:$(ProjectDir) where {port number} is your desired static port number (in this case I have chosen port 1919 and the value is “/port:1919 /path:$(ProjectDir)”).
  • Tick use output window check box
  • Click on the Ok button


Step 3- now that the external tool is added and ready to use you have to change your website project setting to use this web service rather than default web service. To do so
  • Right click on your project file and click on the Property Pages menu.
  • On the left side of the property window click on Start Options.
  • In the Server section choose Use custom server
  • In the base URL text box enter http://localhost:1919 where 1919 should be the port number you have chosen in step 2
  • Click on the Ok button


Step 4- the last step is to start the custom web server before debugging the application. To do so:
  • Click on the Tool menu. Now a new menu item having the name you have assigned to the customer web server in step 2 should be displayed in the tool menu.
  • Click on the new menu item (in this case webserver 1919)

Now you are ready to go. Click F5 and start debugging your web site on a static port.



Differences between web Site and Web Application

by Vahid 10. December 2009 06:05
Have ever wondered what the differences between 2 types of web projects in visual studio 2005 ( web site project and web application project) are?Well personally I had some idea here and there about the differences but when I found the following tables from MSDN which describe the differences in an organized way, I thought of sharing them with you.Just one important thing is missing and this is:In web application project we can assign a static port number for your internal web server whereas in web site project we are restricted to use the dynamically assigned port number. Static port number assignment functionality comes handy in many situation starting from an automated testing.The following table lists Web project options or tasks and indicates which project model best implements those options.

Option or Task

Web Application Projects Web Site Projects
Need to migrate large Visual Studio .NET 2003 applications X  
Prefer single-page code model to code-behind model   X
Prefer dynamic compilation and working on pages without building entire site on each page view (that is, save file and then simply refresh the page in the browser).   X
Need to control names of output assemblies X  
Need to generate one assembly for each page   X
Need stand-alone classes to reference page and user control classes X  
Need to build a Web application using multiple Web projects X  
Need to add pre-build and post-build steps during compilation X  
Want to open and edit any directory as a Web project without creating a project file   X
The following table helps you select a project type by describing some of the key differences between Web application projects and Web site projects.


Web Application Project Web Site Project
Project definition Similar to Visual Studio .NET 2003. Only files that are referenced in the project file are part of the project, are displayed in Solution Explorer, and are compiled during a build. Because there is a project file, some scenarios are more easily enabled: You can subdivide one ASP.NET application into multiple Visual Studio projects.You can easily exclude files from the project and from source code-control. Web site projects use the folder structure to define the contents of the project. There is no project file and all files in the folder are part of the project. This project type is desirable if you have an existing folder structure representing an ASP.NET application that you want to edit in Visual Studio without having to explicitly create a project file.
Compilation and build outputs The compilation model for Web application projects is very similar to that in Visual Studio .NET 2003. All code-behind class files and stand-alone class files in the project are compiled into a single assembly, which is placed in the Bin folder. Because this is a single assembly, you can specify attributes such as assembly name and version, as well as the location of the output assembly.Certain other applications scenarios are better enabled, such as the Model-View-Controller (MVC) pattern, because they allow stand-alone classes in the project to reference page and user control classes. The Build command compiles Web site projects only to test them. To run Web site projects, you deploy source files and rely on ASP.NET dynamic compilation to compile pages and classes in the application. Alternatively, you can precompile the site for performance, which uses the same compilation semantics as ASP.NET dynamic compilation. The ASP.NET dynamic compilation system has two modes—batch mode (the default) and fixed-names mode. In batch mode, many assemblies (typically one per folder) are produced when precompiling the site. In fixed mode, one assembly is produced for each page or user control in the Web site.
Iterative development To run and debug pages, you must build the entire Web project. Building the entire Web application project is usually fast, because Visual Studio employs an incremental build model that builds only the files that have changed. You can configure build options Visual Studio 2005 for when you run the site: build the site, an individual page, or nothing at all. In the last case, when you run a Web site, Visual Studio simply launches the browser and passes to it the current or start page. The request then invokes ASP.NET dynamic compilation. Because pages are compiled dynamically and compiled into different assemblies as needed, it is not required that the entire project compile successfully in order to run and debug a page.By default, Visual Studio completely compiles Web site projects whenever you run or debug any page. This is done to identify compile-time errors anywhere in the site. However, a complete site build can significantly slow down the iterative development process, so it is generally recommended that you change the build project option to compile only the current page on run or debug.
Deployment Because all class files are compiled into a single assembly, only that assembly needs to be deployed, along with the .aspx and .ascx files and other static content files. In this model, .aspx files are not compiled until they are run in the browser. However, when used with Web Deployment Projects (a downloadable add-in to Visual Studio 2005), the .aspx files can also be compiled and included in a single assembly for deployment.Each time you deploy the single assembly produced in this model, you replace the code for all pages in the project. Both .aspx files and code-behind files can be compiled into assemblies using the Publish Website command in Visual Studio. (Note that the Build command does not create a deployable set of assemblies.) The updateable publish option supports compiling only code-behind files while leaving .aspx files unchanged for deployment. The default mode for precompiling produces several assemblies in the Bin folder, typically one per folder. The fixed-names option produces one assembly per page or user control and can be used to create deployable versions of individual pages. However, the fixed-names option increases the number of assemblies and can result in increased memory usage.
Upgrade from Visual Studio .NET 2003 Because the Web application project model is the same as in the Visual Studio .NET 2003, upgrade is generally simple and will usually not require any restructuring of the application. The compilation option for Web site projects is significantly different than Visual Studio .NET 2003. A conversion wizard is available to upgrade existing Visual Studio .NET 2003 Web projects to Web site projects. For any reasonably complex Visual Studio .NET 2003 projects, manual fix-up is usually required after the conversion. For most scenarios, it is preferable to upgrade existing Visual Studio .NET 2003 projects to Web application projects in Visual Studio 2005.

Tags: ,

.Net | Learning resource | Technical

اگر کريستوف کلمب ازدواج کرده بود

by Vahid 9. December 2009 13:26

 اگر کريستوفر کلمب ازدواج کرده بود،شايد هرگز قاره امريکا را کشف نمي کرد، چون بجای برنامه ريزی و تمرکز در مورد چنين سفر ماجراجويانه ای، بايد وقتش را به پاسخ دادن به همسرش، درباره پرسشهای زير مي گذراند :

·         کجا داری ميری؟

·         با کی؟

·         واسه چی؟

·         چطوری دارين می رين؟

·         کشف چی؟

·         چرا فقط تو؟

·         تا تو برگردی من چيکار کنم؟!

·         می تونم منم باهات بيام؟!

·         کِی برمی گردی؟

·         برای شام خونه ای ديگه؟!

·         واسم چی مياری؟

·         تو عمدا اين برنامه رو بدون من ريختی،

·         اينطور نيست؟!

·         جواب منو بده؟

·         من می خوام برم خونه مامانم!

·         من می خوام تو منو اونجا برسونی!

·         ديگه هيچوقت به اين خونه برنمی گردم!

·         منظورت  چيه "اوکی"؟!

·         چرا  جلوم رو نمی گيری؟!

·         من اصلا نمی فهمم اين کشف درباره چی هست؟

·         تو هميشه اينجوری رفتار می کنی!

·         آخرين بار هم همين کار رو کردی!

·         می بينم اين روزها داری يه کارهايی می کنی!

·         من هنوز نمی فهمم، مگه چيز ديگه ايی هم برای کشف کردن مونده!


ظاهرا در مورد اين يک موضوع، تمام فرهنگها به طرز وحشتناکی با هم وجه مشترک دارند.

حالا فکر مي کنيد اون انقدر نابغه بود که مي تونست پاسخ اينهمه پرسشها رو بده و بدون برانگيختن سوظن بره آمريکا رو کشف کنه؟

تازه مي دونيم که اصلا قرار نبود بره آمريکا رو کشف کنه.. قرار بود بره هندوستان.. حالا فکر مي کنيد اگر از آمريکا بر مي گشت و ساری هندی برای زنش نمي اورد و مي گفت من به جای هندوستان رفتم آمريکا رو کشف کردم چه قشقرقي راه مي افتاد.. من که اون موقع اصلا دلم نمي خواست جای اون باشم!!!ا

(به نقل از ایمیل یکی از دوستان)



Maximum Capacity Specifications for SQL Serve 2008

by Vahid 1. December 2009 09:18

 it has been always a question for me that  what the maximum number of table in a sql server database is. searching for an answer to this question, i came across the following table in msdn. i found it very usefull and thought of sharing it with you.

SQL Server Database Engine object

Maximum sizes/numbers SQL Server (32-bit) Maximum sizes/numbers SQL Server (64-bit)
Batch size1 65,536 * Network Packet Size 65,536 * Network Packet Size
Bytes per short string column 8,000 8,000
Bytes per GROUP BY, ORDER BY 8,060 8,060
Bytes per index key2 900 900
Bytes per foreign key 900 900
Bytes per primary key 900 900
Bytes per row8 8,060 8,060
Bytes in source text of a stored procedure Lesser of batch size or 250 MB Lesser of batch size or 250 MB
Bytes per varchar(max), varbinary(max), xml, text, or image column 2^31-1 2^31-1
Characters per ntext or nvarchar(max) column 2^30-1 2^30-1
Clustered indexes per table 1 1
Columns in GROUP BY, ORDER BY Limited only by number of bytes Limited only by number of bytes
Columns or expressions in a GROUP BY WITH CUBE or WITH ROLLUP statement 10 10
Columns per index key7 16 16
Columns per foreign key 16 16
Columns per primary key 16 16
Columns per nonwide table 1,024 1,024
Columns per wide table 30,000 30,000
Columns per SELECT statement 4,096 4,096
Columns per INSERT statement 4096 4096
Connections per client Maximum value of configured connections Maximum value of configured connections
Database size 524,272 terabytes 524,272 terabytes
Databases per instance of SQL Server 32,767 32,767
Filegroups per database 32,767 32,767
Files per database 32,767 32,767
File size (data) 16 terabytes 16 terabytes
File size (log) 2 terabytes 2 terabytes
Foreign key table references per table4 253 253
Identifier length (in characters) 128 128
Instances per computer 50 instances on a stand-alone server for all SQL Server editions except for Workgroup. Workgroup supports a maximum of 16 instances per computer.SQL Server supports 25 instances on a failover cluster. 50 instances on a stand-alone server.25 instances on a failover cluster.
Length of a string containing SQL statements (batch size)1 65,536 * Network packet size 65,536 * Network packet size
Locks per connection Maximum locks per server Maximum locks per server
Locks per instance of SQL Server5 Up to 2,147,483,647 Limited only by memory
Nested stored procedure levels6 32 32
Nested subqueries 32 32
Nested trigger levels 32 32
Nonclustered indexes per table 999 999
Number of distinct expressions in the GROUP BY clause when any of the following are present: CUBE, ROLLUP, GROUPING SETS, WITH CUBE, WITH ROLLUP 32 32
Number of grouping sets generated by operators in the GROUP BY clause 4,096 4,096
Parameters per stored procedure 2,100 2,100
Parameters per user-defined function 2,100 2,100
REFERENCES per table 253 253
Rows per table Limited by available storage Limited by available storage
Tables per database3 Limited by number of objects in a database Limited by number of objects in a database
Partitions per partitioned table or index 1,000 1,000
Statistics on non-indexed columns 30,000 30,000
Tables per SELECT statement Limited only by available resources Limited only by available resources
Triggers per table3 Limited by number of objects in a database Limited by number of objects in a database
Columns per UPDATE statement (Wide Tables) 4096 4096
User connections 32,767 32,767
XML indexes 249 249


Learning resource | SQL | Technical