Visual Studio.NET, Project inside Solution OR Solution inside Project?
-
What do you think about Visual Studio.NET's project and solution structure? Presently, if programmer start a project, e.g. a Windows Application in VB.NET, VS.NET creates Solution and a Project inside it; and later on multiple Projects can be added in the solution. Do you think this is what it should be or VS.NET should create a Project and then add Solution inside it? I think the present structure is not appropriate. VS.NET should create Project and then Solution inside it. The reason behind this opinion is that, programmer has a project/system (problem(s)) and there could be multiple solutions to address one or more of the problems. What I mean is, to build a system which manages data, e.g. a Library, there could be multiple solutions; one for database access, another for user interface, next regarding creating a setup, etc. (What Microsoft could have thought about it when designing VS.NET? In the previous versions, VS 6 and earlier, there was nothing like Solution; programmer had to create multiple projects to address a system. And when Microsoft designed VS.NET, to make the new studio compatible with older structure, they created wrapper, known as Solution, to group projects related to each other. You would be aware that project can be opened directly in VS.NET regardless of existence of its Solution file, the Solution file is automatically created and the opened project is included in it.) So, please, share your thoughts, Solution inside Project or Project inside Solution?
-
Orange??? means?
-
What do you think about Visual Studio.NET's project and solution structure? Presently, if programmer start a project, e.g. a Windows Application in VB.NET, VS.NET creates Solution and a Project inside it; and later on multiple Projects can be added in the solution. Do you think this is what it should be or VS.NET should create a Project and then add Solution inside it? I think the present structure is not appropriate. VS.NET should create Project and then Solution inside it. The reason behind this opinion is that, programmer has a project/system (problem(s)) and there could be multiple solutions to address one or more of the problems. What I mean is, to build a system which manages data, e.g. a Library, there could be multiple solutions; one for database access, another for user interface, next regarding creating a setup, etc. (What Microsoft could have thought about it when designing VS.NET? In the previous versions, VS 6 and earlier, there was nothing like Solution; programmer had to create multiple projects to address a system. And when Microsoft designed VS.NET, to make the new studio compatible with older structure, they created wrapper, known as Solution, to group projects related to each other. You would be aware that project can be opened directly in VS.NET regardless of existence of its Solution file, the Solution file is automatically created and the opened project is included in it.) So, please, share your thoughts, Solution inside Project or Project inside Solution?
It's all a matter of terminology. It sounds like what you think of as a "solution" other people, including Microsoft and myself, think of as a project - and vice versa.
- Life in the fast lane is only fun if you live in a country with no speed limits. - Of all the things I have lost, it is my mind that I miss the most. - I vaguely remember having a good memory...
-
42
I'm beginning to hate the news...the world was much nicer when I was illiterate Be careful which toes you step on today, they might be connected to the foot that kicks your butt tomorrow. You can't scare me, I have children.
Quote:
42
No. That's the answer to the Ultimate Question of... blah, blah, etc.
- Life in the fast lane is only fun if you live in a country with no speed limits. - Of all the things I have lost, it is my mind that I miss the most. - I vaguely remember having a good memory...
-
Please explain how the idea of Project inside Solution is right. And how my focus is on completely irrelevant matter?
They are saying it is irrelevant because it is just the name. Doesn't matter. If it makes more sense to you to have a solution in a project just start calling the solution a project and the projects a solution. At least that is why I think they are saying it is irrelevant. Microsoft could have called it Bing instead and it wouldn't have mattered to me. As long as it opens correctly I could care less what the name is.
-
What do you think about Visual Studio.NET's project and solution structure? Presently, if programmer start a project, e.g. a Windows Application in VB.NET, VS.NET creates Solution and a Project inside it; and later on multiple Projects can be added in the solution. Do you think this is what it should be or VS.NET should create a Project and then add Solution inside it? I think the present structure is not appropriate. VS.NET should create Project and then Solution inside it. The reason behind this opinion is that, programmer has a project/system (problem(s)) and there could be multiple solutions to address one or more of the problems. What I mean is, to build a system which manages data, e.g. a Library, there could be multiple solutions; one for database access, another for user interface, next regarding creating a setup, etc. (What Microsoft could have thought about it when designing VS.NET? In the previous versions, VS 6 and earlier, there was nothing like Solution; programmer had to create multiple projects to address a system. And when Microsoft designed VS.NET, to make the new studio compatible with older structure, they created wrapper, known as Solution, to group projects related to each other. You would be aware that project can be opened directly in VS.NET regardless of existence of its Solution file, the Solution file is automatically created and the opened project is included in it.) So, please, share your thoughts, Solution inside Project or Project inside Solution?
I really don't care very much about what they call those things as long as the names are used consistently and everybody knows what is meant. I have been working on a game just for fun for a while and its solution folder contains 43 separate projects. All this is needed to build two web applications (the game's application logic and data access), four webservices (one each for administration and users for both web applications), a WPF administration client and an XNA user client to play the game. Many of those projects are modules which have been developed in separate solutions. I just need the 3D engine itself for the game and only import this project into the game's solution. Other stuff related to the 3D engine (like tests or related tools) remain in the 3D engine's solution and need not be included into the game. And, since I'm a fan of making things modular, there are quite a few separate solutions like that. I think I really can live with the way things were named.
-
Orange??? means?
Nothing rhymes with orange. I think of it as a "prime word" because it only rhymes with itself.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997 -
Please explain how the idea of Project inside Solution is right. And how my focus is on completely irrelevant matter?
-
What do you think about Visual Studio.NET's project and solution structure? Presently, if programmer start a project, e.g. a Windows Application in VB.NET, VS.NET creates Solution and a Project inside it; and later on multiple Projects can be added in the solution. Do you think this is what it should be or VS.NET should create a Project and then add Solution inside it? I think the present structure is not appropriate. VS.NET should create Project and then Solution inside it. The reason behind this opinion is that, programmer has a project/system (problem(s)) and there could be multiple solutions to address one or more of the problems. What I mean is, to build a system which manages data, e.g. a Library, there could be multiple solutions; one for database access, another for user interface, next regarding creating a setup, etc. (What Microsoft could have thought about it when designing VS.NET? In the previous versions, VS 6 and earlier, there was nothing like Solution; programmer had to create multiple projects to address a system. And when Microsoft designed VS.NET, to make the new studio compatible with older structure, they created wrapper, known as Solution, to group projects related to each other. You would be aware that project can be opened directly in VS.NET regardless of existence of its Solution file, the Solution file is automatically created and the opened project is included in it.) So, please, share your thoughts, Solution inside Project or Project inside Solution?
:doh: Friends, I know it really doesn't matter if there is Project inside Solution OR Solution inside Project. But my question is like if you had a chance to decide the structure of project/solution then what would you do? I am using VS 6 and VS.NET since 2003 but this thing doesn't create any problem, I understand it. So please take it easy. :)
-
What do you think about Visual Studio.NET's project and solution structure? Presently, if programmer start a project, e.g. a Windows Application in VB.NET, VS.NET creates Solution and a Project inside it; and later on multiple Projects can be added in the solution. Do you think this is what it should be or VS.NET should create a Project and then add Solution inside it? I think the present structure is not appropriate. VS.NET should create Project and then Solution inside it. The reason behind this opinion is that, programmer has a project/system (problem(s)) and there could be multiple solutions to address one or more of the problems. What I mean is, to build a system which manages data, e.g. a Library, there could be multiple solutions; one for database access, another for user interface, next regarding creating a setup, etc. (What Microsoft could have thought about it when designing VS.NET? In the previous versions, VS 6 and earlier, there was nothing like Solution; programmer had to create multiple projects to address a system. And when Microsoft designed VS.NET, to make the new studio compatible with older structure, they created wrapper, known as Solution, to group projects related to each other. You would be aware that project can be opened directly in VS.NET regardless of existence of its Solution file, the Solution file is automatically created and the opened project is included in it.) So, please, share your thoughts, Solution inside Project or Project inside Solution?
nikunjbhatt84 wrote:
In the previous versions, VS 6 and earlier, there was nothing like Solution; programmer had to create multiple projects to address a system.
Actually there was a counterpart to the .sln file. It was the .dsw or workspace file. It contained the .dsp or project files. Same concept, new names. Case of rum, case of rum. ;)
BDF I often make very large prints from unexposed film, and every one of them turns out to be a picture of myself as I once dreamed I would be. -- BillWoodruff
-
Nothing rhymes with orange. I think of it as a "prime word" because it only rhymes with itself.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997Quote:
Nothing rhymes with orange
except "Lozenge" or "Sporange" and possibly the place "Stone Henge", or any kind of henge really. "Nothing" certainly doesn't rhyme with "Orange" although it does rhyme with "pushing" if you have a lisp. :laugh:
- Life in the fast lane is only fun if you live in a country with no speed limits. - Of all the things I have lost, it is my mind that I miss the most. - I vaguely remember having a good memory...
-
What do you think about Visual Studio.NET's project and solution structure? Presently, if programmer start a project, e.g. a Windows Application in VB.NET, VS.NET creates Solution and a Project inside it; and later on multiple Projects can be added in the solution. Do you think this is what it should be or VS.NET should create a Project and then add Solution inside it? I think the present structure is not appropriate. VS.NET should create Project and then Solution inside it. The reason behind this opinion is that, programmer has a project/system (problem(s)) and there could be multiple solutions to address one or more of the problems. What I mean is, to build a system which manages data, e.g. a Library, there could be multiple solutions; one for database access, another for user interface, next regarding creating a setup, etc. (What Microsoft could have thought about it when designing VS.NET? In the previous versions, VS 6 and earlier, there was nothing like Solution; programmer had to create multiple projects to address a system. And when Microsoft designed VS.NET, to make the new studio compatible with older structure, they created wrapper, known as Solution, to group projects related to each other. You would be aware that project can be opened directly in VS.NET regardless of existence of its Solution file, the Solution file is automatically created and the opened project is included in it.) So, please, share your thoughts, Solution inside Project or Project inside Solution?
I have my work Projects, each of which I treat as a unit, each has its own 'project root' folder, which may contain docs, database files, stuff, and one or more solutions, in their own folders, Then these contain VS projects, under their solutions, under their Projects.
-
What do you think about Visual Studio.NET's project and solution structure? Presently, if programmer start a project, e.g. a Windows Application in VB.NET, VS.NET creates Solution and a Project inside it; and later on multiple Projects can be added in the solution. Do you think this is what it should be or VS.NET should create a Project and then add Solution inside it? I think the present structure is not appropriate. VS.NET should create Project and then Solution inside it. The reason behind this opinion is that, programmer has a project/system (problem(s)) and there could be multiple solutions to address one or more of the problems. What I mean is, to build a system which manages data, e.g. a Library, there could be multiple solutions; one for database access, another for user interface, next regarding creating a setup, etc. (What Microsoft could have thought about it when designing VS.NET? In the previous versions, VS 6 and earlier, there was nothing like Solution; programmer had to create multiple projects to address a system. And when Microsoft designed VS.NET, to make the new studio compatible with older structure, they created wrapper, known as Solution, to group projects related to each other. You would be aware that project can be opened directly in VS.NET regardless of existence of its Solution file, the Solution file is automatically created and the opened project is included in it.) So, please, share your thoughts, Solution inside Project or Project inside Solution?
When have you ever built a system where you have had multiple solutions to solve a problem? If you have the time to do that, you aren't delivering to a client timescale. Typically, you present one solution to a problem to a client which evolves over time.
*pre-emptive celebratory nipple tassle jiggle* - Sean Ewington
"Mind bleach! Send me mind bleach!" - Nagy Vilmos
CodeStash - Online Snippet Management | My blog | MoXAML PowerToys | Mole 2010 - debugging made easier
-
nikunjbhatt84 wrote:
So, please, share your thoughts, Solution inside Project or Project inside Solution?
Liquid nitrogen or CListCtrl? Any thoughts?
Bacon. Lots and lots of bacon. Pretty much the answer to anything.
Ideological Purity is no substitute for being able to stick your thumb down a pipe to stop the water
-
nikunjbhatt84 wrote:
In the previous versions, VS 6 and earlier, there was nothing like Solution; programmer had to create multiple projects to address a system.
Actually there was a counterpart to the .sln file. It was the .dsw or workspace file. It contained the .dsp or project files. Same concept, new names. Case of rum, case of rum. ;)
BDF I often make very large prints from unexposed film, and every one of them turns out to be a picture of myself as I once dreamed I would be. -- BillWoodruff
Big Daddy Farang wrote:
It was the .dsw or workspace file.
I looked at a project's folder of VB 6 but I didn't find any .dsw file. I googled about the extension and found these two helpful: http://www.fileinfo.com/extension/dsw[^] and http://extension.nirsoft.net/dsw[^]. It seems .dsw is only applicable to VC++ projects, and as I have VB projects, no file is there with .dsw extension. However VB 6 project has .vbw workspace file and it just holds dimensions and/or positions of opened windows/form's of the project, therefore it is not solution file. So, if you are talking about the workspace file of VC++ similar to that of VB then you are missing something :)
-
Please explain how the idea of Project inside Solution is right. And how my focus is on completely irrelevant matter?
- Solutions contain projects so it only makes sense to have the file structure mirror that relationship. 2) It's set up that way by default because that is how most people using the software view this relationship. 3) It's irrelevant because if you don't like it you can change it and do it any which way you like. You could put your solution anywhere you like and your projects anywhere you like. It would make maintenance a nightmare but you can do it.
I wasn't, now I am, then I won't be anymore.
-
What do you think about Visual Studio.NET's project and solution structure? Presently, if programmer start a project, e.g. a Windows Application in VB.NET, VS.NET creates Solution and a Project inside it; and later on multiple Projects can be added in the solution. Do you think this is what it should be or VS.NET should create a Project and then add Solution inside it? I think the present structure is not appropriate. VS.NET should create Project and then Solution inside it. The reason behind this opinion is that, programmer has a project/system (problem(s)) and there could be multiple solutions to address one or more of the problems. What I mean is, to build a system which manages data, e.g. a Library, there could be multiple solutions; one for database access, another for user interface, next regarding creating a setup, etc. (What Microsoft could have thought about it when designing VS.NET? In the previous versions, VS 6 and earlier, there was nothing like Solution; programmer had to create multiple projects to address a system. And when Microsoft designed VS.NET, to make the new studio compatible with older structure, they created wrapper, known as Solution, to group projects related to each other. You would be aware that project can be opened directly in VS.NET regardless of existence of its Solution file, the Solution file is automatically created and the opened project is included in it.) So, please, share your thoughts, Solution inside Project or Project inside Solution?
Ais an object that compiles to an assembly (an.exeor a.dll). A collection of objects of typeAis calledB. Instances of typeAexpose a specific family of functionality. Collectively, these instances (grouped into an instance of typeB) solve a larger problem. It's important to understand that a complex problem is solved by addressing several smaller problems. In Visual Studio,Ais called a "project" andBis called a "solution". These are names that are accepted and understood by the Microsoft developer community in general. /raviMy new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com
-
Bacon. Lots and lots of bacon. Pretty much the answer to anything.
Ideological Purity is no substitute for being able to stick your thumb down a pipe to stop the water
Especially heart problems :)
-
Big Daddy Farang wrote:
It was the .dsw or workspace file.
I looked at a project's folder of VB 6 but I didn't find any .dsw file. I googled about the extension and found these two helpful: http://www.fileinfo.com/extension/dsw[^] and http://extension.nirsoft.net/dsw[^]. It seems .dsw is only applicable to VC++ projects, and as I have VB projects, no file is there with .dsw extension. However VB 6 project has .vbw workspace file and it just holds dimensions and/or positions of opened windows/form's of the project, therefore it is not solution file. So, if you are talking about the workspace file of VC++ similar to that of VB then you are missing something :)
nikunjbhatt84 wrote:
you are missing something
Lot's of things, actually! :laugh: I never used VB 6, so I didn't know that. VS 6 would also allow you to open the .dsp project file directly, as you described earlier, and create a .dsw file for you if it didn't already exist. Assuming VC ++, of course. Hopefully this provided a bit of historical perspective for both of us. :)
BDF I often make very large prints from unexposed film, and every one of them turns out to be a picture of myself as I once dreamed I would be. -- BillWoodruff
-
What do you think about Visual Studio.NET's project and solution structure? Presently, if programmer start a project, e.g. a Windows Application in VB.NET, VS.NET creates Solution and a Project inside it; and later on multiple Projects can be added in the solution. Do you think this is what it should be or VS.NET should create a Project and then add Solution inside it? I think the present structure is not appropriate. VS.NET should create Project and then Solution inside it. The reason behind this opinion is that, programmer has a project/system (problem(s)) and there could be multiple solutions to address one or more of the problems. What I mean is, to build a system which manages data, e.g. a Library, there could be multiple solutions; one for database access, another for user interface, next regarding creating a setup, etc. (What Microsoft could have thought about it when designing VS.NET? In the previous versions, VS 6 and earlier, there was nothing like Solution; programmer had to create multiple projects to address a system. And when Microsoft designed VS.NET, to make the new studio compatible with older structure, they created wrapper, known as Solution, to group projects related to each other. You would be aware that project can be opened directly in VS.NET regardless of existence of its Solution file, the Solution file is automatically created and the opened project is included in it.) So, please, share your thoughts, Solution inside Project or Project inside Solution?
"Gold Jacket, Green Jacket, who gives a sh*t." - Happy Gilmore
CPallini wrote:
You cannot argue with agile people so just take the extreme approach and shoot him. :Smile:
