Blog Moved ....

ScottCate.com

community

frenz

my book(s)

my products

July 2007 - Posts

St. Louis .NET User Group (July 30, 2007, 5:30pm)

With the help of the INETA.org speakers bureau, I've made my way to St. Louis to talk to the local user group about the MVP (Model View Presenter) design pattern. Every time I deliver this talk, it get's better and better. If you're within driving distance to St. Louis, and are programming in .net, this is a great talk and would prove to be beneficial. I've delivered the talk many times, as well as written blog entries on the topic, but there is nothing quite like seeing it in person.

Here is a link to the user group site for directions, which will guide you to Microsoft building in St. Louis.

And to save a click, here is a direct link to the map with the address and directions.

[UPDATE 2007 07July31 10:27am]
The source code that we created for this talk is now uploaded and available for download as STL-MVP.zip. In the root of this zip file is an STL.sql file, that can be used to create the table in a database on your machine. After this is done, change the connection string in STL.Data/app.config and you're project should come alive just fine.

How do you setup a family of .net assemblies that can see each others internals?

I've always put my unit tests in a separate assembly/project, so they don't mingle with shipped production code (although I've read that some like to ship the test for debugging purposes). So let's say I have ProjectA.DLL in it is a class.

internal class DoSomethingSecret {} How do you write a test for that in ProjectA.Test.DLL? I think the answer also involves my next (and the real) question.

Since I started programming in .net, I've not like the public keyword. It just seems so open to the world; but it's been my only gateway for communicating across my own assemblies. I know there is a way to setup a group of (signed??) assemblies as a family, but I don't know how to do it. In this scenario (I'm guessing/hoping), each family member (assembly) can see the internal methods of their relatives?

With this solution, I'll be able to have a group of assemblies that can see the internal methods of each other, and I can mark most of the classes, methods internal. And the only markings of public, are truly items/signatures that I want to expose to the world.

Thanks for your pointers.

[UPDATE :: Solution]
Thanks for the quick comments. This article by Matthew Cochran offers the perfect solution.

Posted: Jul 19 2007, 09:55 AM by scott cate | with 6 comment(s)
Filed under: ,
More Posts