T
TheMilitarian
Guest
Im fairly new to VS2K13 & .Net, so Im only asking for some directional advice on what articles I could read up on and what search engine terminology I could be looking for.
Whats this for:
Im trying to build a VB class library VS project to extend the functionality around a COM library add-in for my front-end application. This COM library is based on an dev toolkit for connecting to Salesforce\CRM and is quite heavy on the use of multi-dimensional VariantTypes. Im trying to create strong typed class objects/wrappers so I can design a more fluid ETL process and limit disk I/O bottlenecks when writing to cached data source objects.
My Challenge:
I stuck on trying to figure out how to build a better method for instantiating a base class which requires passing a COM Object into it so it can read/validate/manipulate properties and children entities of that COM object for adding as a reference in my VS console application. The desired result is to limit redundant error handling procedures by making sure a base class has an active COM object set by a public property before Intellisense (Prior to Run Time) displays any of the dependent properties.
Is this possible and if so, could someone point me to a few research topics to read up on or KB articles that might help me achieve what Im looking for? Maybe I need some .Net foundation training but Id be really grateful for any tips or suggestions.
This is my sample Base class
Public Class iSObject
Private pObj As SForceOfficeToolkitLib4.SObject4
SObject(): The client provider referencing this library must set this object before any of its other properties are accessible
Public Property SObject() as SForceOfficeToolkitLib4.SObject4
Get
Return pObj
End Get
Set(value as SForceOfficeToolkitLib4.SObject4)
pObj = value
End Set
End Property
Name(): Obviously this only returns a value *If NOT pObj Is Nothing*. I know I could validate if pObj is nothing and return vbnullstring. Im trying to figure out how I could prevent intellisense from displaying these properties if my base object of this class pObj is not set or throw out an exception or error so the client provider can logically use its own error handler w/o breaking and dumping values cached in the memory.
ReadOnly Property Name() as String
Get
Return pObj.ObjectType Returns entity name
End Get
End Property
End Class
Continue reading...
Whats this for:
Im trying to build a VB class library VS project to extend the functionality around a COM library add-in for my front-end application. This COM library is based on an dev toolkit for connecting to Salesforce\CRM and is quite heavy on the use of multi-dimensional VariantTypes. Im trying to create strong typed class objects/wrappers so I can design a more fluid ETL process and limit disk I/O bottlenecks when writing to cached data source objects.
My Challenge:
I stuck on trying to figure out how to build a better method for instantiating a base class which requires passing a COM Object into it so it can read/validate/manipulate properties and children entities of that COM object for adding as a reference in my VS console application. The desired result is to limit redundant error handling procedures by making sure a base class has an active COM object set by a public property before Intellisense (Prior to Run Time) displays any of the dependent properties.
Is this possible and if so, could someone point me to a few research topics to read up on or KB articles that might help me achieve what Im looking for? Maybe I need some .Net foundation training but Id be really grateful for any tips or suggestions.
This is my sample Base class
Public Class iSObject
Private pObj As SForceOfficeToolkitLib4.SObject4
SObject(): The client provider referencing this library must set this object before any of its other properties are accessible
Public Property SObject() as SForceOfficeToolkitLib4.SObject4
Get
Return pObj
End Get
Set(value as SForceOfficeToolkitLib4.SObject4)
pObj = value
End Set
End Property
Name(): Obviously this only returns a value *If NOT pObj Is Nothing*. I know I could validate if pObj is nothing and return vbnullstring. Im trying to figure out how I could prevent intellisense from displaying these properties if my base object of this class pObj is not set or throw out an exception or error so the client provider can logically use its own error handler w/o breaking and dumping values cached in the memory.
ReadOnly Property Name() as String
Get
Return pObj.ObjectType Returns entity name
End Get
End Property
End Class
Continue reading...