Tone's Notes

Opened by ToneEngel on 2005-06-16 at 06:02:59    
On the Settings tab of the application Properties GUI the Browse... option on the Type column combo box brings up a Select a Type dialog that does not include types defined in all referenced assemblies or types defined in the application project.

Beta 1 allowed these types to be selected for property settings and the functionality worked. After conversion to beta 2, these user types appear in the combo box list, but not the browse list.

Manually editing the settings XML file can cause the types to appear in the combo box list.

Edited by Microsoft on 2005-06-17 at 00:25:17

The Microsoft Sub-status is now "Reproduced"

Thanks for reporting this bug, we have been able to repro this issue and are investigating.

Thank you,
Vivek, VS2005 Product Team.

Resolved as Won't Fix by Microsoft on 2005-06-24 at 10:37:11

The issue with using types from referenced assemblies showing up was found too late to be fixed in the Beta2 release (see http://lab.msdn.microsoft.com/ProductFeedback/viewFeedback.aspx?feedbackid=45bfedf6-825b-478b-861e-c2be77bcbdd9) It has been fixed since, and using types from referenced assemblies will work in the RTM release of Visual Studio 2005.

Being able to use types defined in the current project is a very good suggestion, but given our current schedule, we will unfortunately not have time to address this in the Visual Studio 2005 release. I will make sure that we revisit this for the next release of Visual Studio.

There are inherent problems with types that are defined in the same project/in project-to-project references in that they are very likely to change. The settings designer actually has to be able to create instances of the current type in order to function correctly (it needs that information in order to be able to show you the right editor, if any, to edit values as well as to be able to write the default values in code and in the app.config file).

As a work-around, if you really need to use types defined in the current project, you can use the user-editable part of the settings class (the file that opens if you push "View Code" in the settings design) and manually add the settings to this class:

<Global.System.Configuration.UserScopedSettingAttribute(), _
Global.System.Configuration.DefaultSettingValueAttribute("(Optional) serialized representation of an instance of this type")> _
Public Property Setting() As MyTypeDefinedInTheCurrentProject
Get
Return CType(Me("Setting"),MyTypeDefinedInTheCurrentProject)
End Get
Set
Me("Setting") = value
End Set
End Property

As of June 22^nd of this year, if you were formerly a Fleet Bank personal checking account customer who used online banking, your ability to write “personal checks” was taken from you by Bank of America and replaced by something quite different.

When you write someone a personal check, the money stays in your account until the check is presented to the bank for payment, at which time the funds are transferred from your account to the recipient’s account or to cash. If you send your nephew Jimmy a birthday card with a personal check which gets lost in the shuffle, the money stays in your account. If you send someone a check and they refuse to accept it, the funds stay in your account.

When you reconcile your checking account statement it’s easy to spot which checks may have been lost or declined.

This is exactly the way online check writing used to work under the Fleet Bank system.

On June 13^th, Bank of America shut down Fleet Bank’s original online payment system and invited all of us to register for their own system a week later on the 22^nd. What may not have been at all clear from the paperwork explaining the transition is that the new checks you are now writing are essentially cashier’s checks.

If you’ve ever used a cashier’s check, also known as a bank check, you know that it is quite different from a personal check. While I can write a personal check for more than is currently in my account (assuming I know a deposit will be arriving before the check will be cashed) a bank check requires that the funds are in my account at the time the check is written. The funds are withdrawn from my account when the check is created; permitting the bank to guarantee that the check will not bounce.

The downside to a bank check is that if the check is lost, stolen, or declined by the recipient, the money stays missing from my account. Unless I hear about what happened to the check by other means, I will never know that it did not reach its intended recipient. If the check is lost or refused, the money may sit in the bank’s special fund for uncollected cashier’s checks for a very long time.

I expect that it is exactly this period of time – between requesting the check and its collection – that permits Bank of America to offer online banking at no additional monthly charge. It takes a minimum of two to five days for a check to be sent. Additional days or weeks may pass before paper checks are returned to the bank for collection. During all that time, the bank can arrange to earn interest on these funds for their own benefit.

If you understand these changes and make adjustments in how you use online banking (don’t send Jimmy an online check), Bank of America’s system may continue to make sense for you. The transition may make sense given the increasing percentage of all electronic transactions.

As always, it pays to read the fine print.