>>I am thinking of how better organize some files in the ASP.NET 4.0 project. The project will use datasets (xsd) files. So my questions are:
>>1. Will I have to copy the .xsd file to the customer server when deploying the application?
>No
>>2. Is it a good idea to create a separate folder for all DataSets (xsd) that will be used in the project?
>Only from the POV of readability in Solution Explorer.
>
>Might be a good idea to put all this stuff in a separate project as the DL?
>
>Also might be a good idea to use EntityFramework instead - but that's a whole different topic :-}
I thought about putting the DataSet into a different project but didn't see (right now) much benefit in doing it. These DataSets will not be reused in another solution. Mostly, as you correctly pointed, I want the Solution Explorer to be better organized. And I think (after I posted the message) that the .XSD files will be included in the .DLL that will be deployed. So I won't have to copy them to server during deployment.
As to EntityFramework, I am not ready yet for it. You are right; this is a different topic :)
Thank you very much for your help.
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham