 |
BOOK: Beginning ASP.NET 4.5 : in C# and VB
 | This is the forum to discuss the Wrox book Beginning ASP.NET 4.5: in C# and VB by Imar Spaanjaars; ISBN: 978-1-118-31180-6 |
Welcome to the p2p.wrox.com Forums.
You are currently viewing the BOOK: Beginning ASP.NET 4.5 : in C# and VB section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
|
|
|
|
|

August 20th, 2013, 08:17 PM
|
|
Authorized User
|
|
Join Date: Aug 2012
Posts: 39
Thanks: 4
Thanked 1 Time in 1 Post
|
|
Chapter 2: Building An ASP.NET Website
Hello,
I have fully read this chapter and was expecting some mention of this Visual Studio 2012 phenomenon in one of the following sections:
Different Project Types
Choosing the Right Website Template
Creating and Opening a New Wesbite
When creating a new website, working with it and then closing it, Visual Studio Express 2012 for Web sometimes prompts the user to save a solution! This is after all website files have been saved, and I'm preparing to close the IDE. I have reset the IDE to the defaults, with no effect. I do not know what is causing this, or if this is expected behaviour. I have been simply choosing no.
Do you have any comment or insight into this ?
Thank you.
WebDev123
|
|

August 21st, 2013, 08:00 AM
|
 |
Wrox Author
|
|
Join Date: Jun 2003
Posts: 17,089
Thanks: 80
Thanked 1,576 Times in 1,552 Posts
|
|
Hi there,
A Solution (identified by a .sln extension) is a Visual Studio container to hold projects (and web sites). Usually, when working with a single web site, Visual Studio will manage the .sln file for you automatically. For some reason, however, it sometimes prompts you to save it. You can safely do so and it will use the file you specify from then on.
Multi-project solutions that contain multiple projects always require an explicit solution file.
Cheers,
Imar
|
|

August 21st, 2013, 08:57 PM
|
|
Authorized User
|
|
Join Date: Aug 2012
Posts: 39
Thanks: 4
Thanked 1 Time in 1 Post
|
|
Okay, so is there any difference or penalty if you do not save the .sln file ?
And if you do, can you save it into your simple website project folder (such as "C:\BegASPNET45\Site" for example) to keep things all in one place ? Or, do you have to save it outside of that folder?
Also, I've noticed two scenarios when being prompted ...
1) You are prompted to save a solution (.sln) file named YourProject.sln.
2) You are prompted to save a solution (.sln) file named localhost...sln, as if it wants you to save a IIS solution file. I don't understand that.
Are these equivalent ?
Thanks-
|
|

August 22nd, 2013, 02:45 AM
|
 |
Wrox Author
|
|
Join Date: Jun 2003
Posts: 17,089
Thanks: 80
Thanked 1,576 Times in 1,552 Posts
|
|
>> Okay, so is there any difference or penalty if you do not save the .sln file ?
No, not that I know, other than that you're not prompted every time, You could also save it explicitly through the File menu.
>> as if it wants you to save a IIS solution file. I don't understand that.
It doesn't. Solution Files are always specific to Visual Studio. My guess is that the name it chooses depends on how you open or create the web site.
Cheers,
Imar
|
|
 |
|