Syndication Ads

Coordinator
Jun 27, 2006 at 9:29 AM
Would you please add a new project for my "Syndication Ads" CSModule?
I'm to upgrade/change it for 2.1.

+ Also if it's possible please enable email notifications for all new items on this project.
Coordinator
Jun 27, 2006 at 12:24 PM
Ok, I added email notifications for myself.
Coordinator
Jun 27, 2006 at 12:53 PM
I added my SyndicationAds CSModule as well. Please give a constant pattern for all AssemblyInfo files.
I've added mine. What's your idea?
Coordinator
Jun 27, 2006 at 7:01 PM
Looked at your asemblyinfo looks good!

Should each folder/CSModule have it's own bin folder, or should there be one common for all?
Coordinator
Jun 27, 2006 at 7:20 PM
For now, it's better to compile CSModules into separate files (it's absolutely easier to test) but for deployment we can decide to add a single project and DLL file for all or not.
Coordinator
Jun 27, 2006 at 9:31 PM
Thinking of it, we could have one global solution (SLN) file, and each folder have it's own project file (w supporting source code files).

If we do that now or later, I don't know. What happens when we make a release without a combined SLN file?
Coordinator
Jun 28, 2006 at 3:26 AM
Please do whatever you think it's better and define the structure, then inform us to add our files based on that structure.
Having a global solution + same binaries have some limitations: Once we find some changes in APIs, they can probably cause errors in old MODs. Anyway, whatever you think ;-)
Coordinator
Jun 28, 2006 at 6:04 AM
I don't want to do just whatever I think. :-) That's why I am asking. To have a discussion on how we do this in the best way. I might not be aware of all issues "my ideas" would give, and I need input on that.

I would like for us to find the best structure for this. What would be your suggestion for the global strucutre of all the projects?
Coordinator
Jun 28, 2006 at 6:10 AM
;-)

For now it doesn't matter how we implement. We can start coding and after a while we can decide on structure based on our needs. We can create separate folders for each CSModule and add files to it. After testing and finishing, we can create a global structure and deploy all CSModules in it.
Coordinator
Jun 28, 2006 at 10:47 AM
If you agreed, I'll remove my files and you do the same. Then you setup the structure and we can repload our files later. You can setup one solution which consists of several projects or create several separate projects. The first approach is better, I think.
Coordinator
Jun 28, 2006 at 10:05 PM
I couldnt get my network to work again tonight. I am currently running via GPRS on my phone. I'll get home tomorrow evening from my customer visit. Then I'll remove the files and set up some initial structure.
Coordinator
Jun 29, 2006 at 8:15 AM
NP, I did it.
Now we have a new structure. Once you confirmed it, I'll start coding ;-)

Don't forget to open solutions on our local machine because they have Solution Folders which won't be shown as physical folders.
Coordinator
Jun 29, 2006 at 11:16 AM
Ok, never mind my post in another post here where I say I will delete it.

I'll look at it tonight then.
Coordinator
Jun 29, 2006 at 5:22 PM
>>Don't forget to open solutions on our local machine because they have Solution Folders which won't be shown as physical folders.

I'm confused :-)

I opened the .SLN file at $/CSModulesRepository/CS2.0/CSMVPs.CSModules20, and bound it locally to the Team Server source control. Is that what you mean?
Coordinator
Jun 29, 2006 at 6:43 PM
If did it right, you should see VB and CSharp folders in your solution and projects into them.
Coordinator
Jun 29, 2006 at 6:50 PM
This is how it looks:

<img src="http://static.flickr.com/70/177854507_be83b7f220.jpg" width="287" height="414" />

I always have to open the .SLN from Solution Explorer
Coordinator
Jun 30, 2006 at 1:12 AM
That's Ok but you should be able to use Open Exisiting Project at start up, go to your mapped folder and choose the solution.

Later this should be shown in your projects list at start up. This isn't related to TFS issues.