All that amounts to is a simple interface with things that are applicable to both lots and developed land. So based on that, we can have a signature set that is implemented in 2 other classes.
//Written by Joseph I. Szweda
//July 6, 2009
//This is a class that implements the IMobsterRealEstate
//interface for developed land.
using System;
using System.Collections.Generic;
using System.Text;
namespace MobstersRealEstate
{
class MobstersDevlopedLand : MobsterRealEstate.IMobsterRealEstate
{
//Construct
MobstersDevlopedLand()
{
}
//Destructor
~MobstersDevlopedLand()
{
}
//locals
private string m_strRealEstateName;
private int m_intRealEstateQuantity;
private int m_intBaseCost;
private int m_intIncome;
private int m_intCurrentPrice;
private decimal m_decReturnOnInvestment;
private int m_intLevelAvailableAt;
#region IMobsterRealEstate Members
string MobsterRealEstate.IMobsterRealEstate.strRealEstateName
{
get
{
//throw new Exception("The method or operation is not implemented.");
return this.m_strRealEstateName;
}
set
{
//throw new Exception("The method or operation is not implemented.");
this.m_strRealEstateName = value;
}
}
int MobsterRealEstate.IMobsterRealEstate.intRealEstateQuantity
{
get
{
//throw new Exception("The method or operation is not implemented.");
return this.m_intRealEstateQuantity;
}
set
{
//throw new Exception("The method or operation is not implemented.");
this.m_intRealEstateQuantity = value;
}
}
int MobsterRealEstate.IMobsterRealEstate.intBaseCost
{
get
{
//throw new Exception("The method or operation is not implemented.");
return this.m_intBaseCost;
}
set
{
//throw new Exception("The method or operation is not implemented.");
this.m_intBaseCost = value;
}
}
int MobsterRealEstate.IMobsterRealEstate.intIncome
{
get
{
//throw new Exception("The method or operation is not implemented.");
return this.m_intIncome;
}
set
{
//throw new Exception("The method or operation is not implemented.");
this.m_intIncome = value;
}
}
int MobsterRealEstate.IMobsterRealEstate.intCurrentPrice
{
get
{
//throw new Exception("The method or operation is not implemented.");
return this.m_intCurrentPrice;
}
set
{
//throw new Exception("The method or operation is not implemented.");
this.m_intCurrentPrice = value;
}
}
decimal MobsterRealEstate.IMobsterRealEstate.decReturnOnInvestment
{
get
{
//throw new Exception("The method or operation is not implemented.");
return this.m_decReturnOnInvestment;
}
set
{
//throw new Exception("The method or operation is not implemented.");
this.m_decReturnOnInvestment = value;
}
}
int MobsterRealEstate.IMobsterRealEstate.intLevelAvailableAt
{
get
{
//throw new Exception("The method or operation is not implemented.");
return this.m_intLevelAvailableAt;
}
set
{
//throw new Exception("The method or operation is not implemented.");
this.m_intLevelAvailableAt = value;
}
}
#endregion
}
}
Then for developed land, we can see the reuse of the same interface:
//Written by Joseph I. Szweda
//July 6, 2009
//This is a class that implements the IMobsterRealEstate
//interface for undeveloped land.
using System;
using System.Collections.Generic;
using System.Text;
namespace MobstersRealEstate
{
class MobstersUndevlopedLand:MobsterRealEstate.IMobsterRealEstate
{
//Construct
MobstersUndevlopedLand()
{
}
//Destructor
~MobstersUndevlopedLand()
{
}
//locals
private string m_strRealEstateName;
private int m_intRealEstateQuantity;
private int m_intBaseCost;
private int m_intIncome;
private int m_intCurrentPrice;
private decimal m_decReturnOnInvestment;
private int m_intLevelAvailableAt;
#region IMobsterRealEstate Members
string MobsterRealEstate.IMobsterRealEstate.strRealEstateName
{
get
{
//throw new Exception("The method or operation is not implemented.");
return this.m_strRealEstateName;
}
set
{
//throw new Exception("The method or operation is not implemented.");
this.m_strRealEstateName = value;
}
}
int MobsterRealEstate.IMobsterRealEstate.intRealEstateQuantity
{
get
{
//throw new Exception("The method or operation is not implemented.");
return this.m_intRealEstateQuantity;
}
set
{
//throw new Exception("The method or operation is not implemented.");
this.m_intRealEstateQuantity = value;
}
}
int MobsterRealEstate.IMobsterRealEstate.intBaseCost
{
get
{
//throw new Exception("The method or operation is not implemented.");
return this.m_intBaseCost;
}
set
{
//throw new Exception("The method or operation is not implemented.");
this.m_intBaseCost = value;
}
}
int MobsterRealEstate.IMobsterRealEstate.intIncome
{
get
{
//throw new Exception("The method or operation is not implemented.");
return this.m_intIncome;
}
set
{
//throw new Exception("The method or operation is not implemented.");
this.m_intIncome = value;
}
}
int MobsterRealEstate.IMobsterRealEstate.intCurrentPrice
{
get
{
//throw new Exception("The method or operation is not implemented.");
return this.m_intCurrentPrice;
}
set
{
//throw new Exception("The method or operation is not implemented.");
this.m_intCurrentPrice = value;
}
}
decimal MobsterRealEstate.IMobsterRealEstate.decReturnOnInvestment
{
get
{
//throw new Exception("The method or operation is not implemented.");
return this.m_decReturnOnInvestment;
}
set
{
//throw new Exception("The method or operation is not implemented.");
this.m_decReturnOnInvestment = value;
}
}
int MobsterRealEstate.IMobsterRealEstate.intLevelAvailableAt
{
get
{
//throw new Exception("The method or operation is not implemented.");
return this.m_intLevelAvailableAt;
}
set
{
//throw new Exception("The method or operation is not implemented.");
this.m_intLevelAvailableAt = value;
}
}
#endregion
}
}
That's basically the very basic code and format I am using to start to frame things up. The nice thing about this is a few things that no employer or PM I've met seems to really understand or care too.
1. This is reusable.
2. It's generic. I can implement this into a web site with ease. I can use it for a Windows client, or both.
3. With a little documentation, you can easily reference the assembly, and make your own custom implementation of the same business object with the same interface. You just pass in an instance of the IMobstersRealEstate interface, and it will work so long as your references are right.
I have some other classes to work on, some custom exception handlers that will go along with these, and of course some validators.
I am still trying to rethink the architecture in comparison to the last Windows based project I did. There is no real data layer, but there is an XML layer. So things are a little backwards in comparison to how you do these things.
I have an XML API that I wrote. The issue is that for me to populate and serialize XML, I would have to inherit my class. Well, that starts to look like a data access tier, so maybe I ought to clone this. If I do, there will be one aspect that is a clone that inherits the API, and perhaps another that inherits some validator classes. It's either that or I have some delegates to stick in.
The thing is if I start using delegates, I fear a mish mosh of data access and business objects. All I really want is a 2 fold thing. I want to be able to access certain XML files in a granular format to minimize maintenance as the game has new items so that the user can simply enter what they want, it gets serialized, the end. Think it's a pipe dream? So did a client I once had before. I made it happen, and I can reuse the same technology here.
So here is the way I envision this working. Have something that inherits my XML API for data access, and maybe modify the constructs for the clones to be instantiated with another object instance of like kind from the parent clone in the data tier. Then I can have a bona fide data access tier, and I can have something to accept data from my presentation tier without intermingling the two.
Yes, it's 2 copies of the same thing-maintenance. However, if I implement this right, and reuse the same exact interfaces, it's really 2 different implementations of the same interface. So...that kinda solves itself or at least most of the headaches there. 
As for all the calculations and things, that's all going to live in dedicated business tiers. That's all there is to it. It's a lot easier than using macro's and stinky script. Also, I have an idea for a Mogul Version for the extreme real estate moguls that would use SQL Express in addition to what I propose. That would make n-tier a must. That might be a bit overboard, but there is a point to doing that for certain short sale tactics and such. :-)
So...it's back to architecting more interfaces, DLL's, validators, and of course custom collections to be used by the bussiness tier.
Happy mobbing...and stay tuned.
-joe
Member Buzz
1 day 11 hours ago
1 day 12 hours ago
3 days 13 hours ago
3 days 15 hours ago
3 days 16 hours ago
3 days 17 hours ago
3 days 18 hours ago
3 days 21 hours ago
4 days 6 hours ago
4 days 6 hours ago