BulkEdit V2.53 Available

- Fixed old bugs in XML Import of Purchase Currency
- Added Cancel button to all menus with progress bars to allow interruption of long tasks
- Added Purchase Date, Purchase Place, Purchase Price and Purchase Currency to Bulk Import of Personal Data
- Collection\Flagged\Flag Children changed to remove parent flags before flagging the children

Here is the exact set of header fields recognized:

"profileid", "disc", "location", "slot", "notes", "prenotes", "postnotes", "collectiontype", "collection#", "purchasedate", "purchaseplace", "purchaseprice", "purchasecur"

For Purchase Currency, you may use any of the following ways:

- Full text of Purchase Currency dropdown (e.g. "United States (Dollar)", "Denmark (Krone)", etc.)
- The country portion, up to the "(" symbol (e.g. "Great Britain" or "Japan", etc.)
- The denomination sysbol, as used by DVDP XML Export, (e.g. "USD", "JPY", "GBP", etc.)
- "$" in lieu of "USD"
- "£" in lieu of "GBP"
- "€" in lieu of "Euro"
- "¥" in lieu of "JPY"

For convenience, here is a code snippet that reveals the complete list of currencies recognized:

                currencymap.Add("ARP", "Argentina (Peso)");
                currencymap.Add("AUD", "Australia (Dollar)");
                currencymap.Add("BRL", "Brazil (Real)");
                currencymap.Add("CAD", "Canada (Dollar)");
                currencymap.Add("CLP", "Chile (Peso)");
                currencymap.Add("CNY", "China (Renminbi)");
                currencymap.Add("DKK", "Denmark (Krone)");
                currencymap.Add("€", "Europe (Euro)");
                currencymap.Add("£", "Great Britain (Pound)");
                currencymap.Add("HKD", "Hong Kong (Dollar)");
                currencymap.Add("ISK", "Iceland (Krona)");
                currencymap.Add("INR", "India (Rupee)");
                currencymap.Add("IDR", "Indonesia (Rupiah)");
                currencymap.Add("ILS", "Israel (Shekel)");
                currencymap.Add("¥", "Japan (Yen)");
                currencymap.Add("MYR", "Malaysia (Ringgit)");
                currencymap.Add("MXP", "Mexico (New Peso)");
                currencymap.Add("NZD", "New Zealand (Dollar)");
                currencymap.Add("NOK", "Norway (Krone)");
                currencymap.Add("PHP", "Philippines (Peso)");
                currencymap.Add("RUR", "Russia (Rouble)");
                currencymap.Add("SGD", "Singapore (Dollar)");
                currencymap.Add("ZAR", "South Africa (Rand)");
                currencymap.Add("KRW", "South Korea (Won)");
                currencymap.Add("SEK", "Sweden (Krona)");
                currencymap.Add("CHF", "Switzerland (Franc)");
                currencymap.Add("TWD", "Taiwan (Dollar)");
                currencymap.Add("THB", "Thailand (Baht)");
                currencymap.Add("TRL", "Turkey (1 million Lira)");
                currencymap.Add("$", "United States (Dollar)");
                currencymap.Add("USD", "United States (Dollar)");
                currencymap.Add("JPY", "Japan (Yen)");
                currencymap.Add("EUR", "Europe (Euro)");
                currencymap.Add("GBP", "Great Britain (Pound)");

I downloaded and installed it last week.
I have only used it once and it worked fine for me!

Thanks for the update!!

Ok, I am posting this in case it helps people in the future

I have a laptop with Windows 8 64 bit.  I installed the latest security updates the other day (and there were some for .NET) and after the updates DBDP would have an APPCRASH on startup.  And then when I would start it up again it would come up with the dialogue asking if I wanted normal or diagnostic startup.  Well it would only start if I started it with no plugins.

I uninstalled all the plugins and it came up.  After installing each plug in one at a time, stopping and starting DVDP I determined that the BE plugin was at fault.  I actually did this determination in many more methodical steps that I am stating to give mediadogg all the information I could.  But I am truncating that for this post.

Well I PM'd the dog...

He thought about it and then asked if it had anything to do with this post http://www.invelos.com/Forums.aspx?task=viewtopic&topicID=295144&PageNum=39&messageID=2180858#M2180858

Well I have never had the CCV plugin, but the fact that the 'C:\Users\[USERNAME]\AppData\Local\Invelos_Software\DefaultDomain_Path_[a lot of letters]\1.0.0.0\user.config file was in question got me curious

But I thought possibly what if there is an issue with that config file

So I opened 'C:\Users\[USERNAME]\AppData\Local\Invelos_Software\DefaultDomain_Path_[a lot of letters]\1.0.0.0\user.config'

And in there were default values based on the last time I used BE.

I deleted the XML for the BE configs from that file

I installed BE and DVDP comes up

Now I don't know what the MS updates had to do with that config file and causing BE to crash.  But initializing the config settings  make it install and work.

So possibly the CCV issue is really an issue with that config file or config entries.

At any rat it is working.  So if you all get initialization APP crashes try this.

Quoting Scooter1836:

Quote:
Well I have never had the CCV plugin, but the fact that the 'C:\Users\[USERNAME]\AppData\Local\Invelos_Software\DefaultDomain_Path_[a lot of letters]\1.0.0.0\user.config file was in question got me curious

The problem is not caused only by my CCVPlugin, but it can be any plugin, which is compiled against a higher .NET Framework version than 2. If the first plugin you ever installed is compiled in .NET 3 or 4, then all other plugins which use .NET 2 do not work anymore, except if you delete the config file.
If you install first a .NET 2 plugin and then the others, it works.
Seems Microsoft forgot in .NET 2 to consider that multiple .NET frameworks can be used in the same process, if .NET is used in plugins, but not in the main program.

What happens is, that the first .NET plugin creates the config file, and all others append there config settings there. But if, for example, a .NET 4 plugin creates this file, a .NET 2 plugin cannot read the format. The other way around it works. A .NET 4 plugin can read a .NET 2 config file.

Quoting mediadogg:

Quote:
Thanks Tom. Now I remember that you explained this to me before. I think it's about time for me to move up to .NET 4. But does that also mean I cannot support users on Windows XP?

.NET 4 Framework is available for Windows XP. My tools are working on Windows XP.
If you move to .NET 4, it just means that they may be some users who also have to install a new .NET Framework.

As a matter of fact, .NET 2 may cause problems on Windows 8. As far as I know, you have to activate the .NET legacy support on Windows 8 for it to work.

OK, sold. Will move to NET 4. I'll probably avoid LINQ for the moment. One step at a time. Thanks again for the analysis. By the way, I have several Windows 8 machines - in fact I test and compile all my plugins on it. Go figure.

Actually, I don't think that is the case in general. NET 4 should include support for NET 2 applications. I have never had to do anything special, and almost all of my plugins are NET 2. I have run my plugins on almost every version of Widows (TechNet subscription), and Windows Servers, with no issues that I can attribute to the version (Vista excepted). So, I definitely think there are some nuances that, I for one, do not fully understand. All that being said, I do intend to migrate BulkEdit to NET 4.

Quoting mediadogg:

Quote:
BulkEdit V2.54 Available

- Recompiled to Net 4.0
- Removed Headshots menu (experiment exposed by mistake)

I will install and check this out in a few...My Hunger Games: Catching Fire came and that takes precedence LOL