![]() ![]() If you get the Premium version of Visual Studio, you've got a higher SKU than the Professional version. NET Framework Team agrees and they've said that will be following now so the next small release will be 4.0.2! However I may be perceived as Chicken Little as I haven't personally collected broad community opinion. I've met with that team, and encouraged them to stick with Semantic Versioning and call these updates. First, Platform Update "1" implies a future Platform Update "N+1." Second, when something that is a platform called 4.0 is updated, you'd expect it to be called 4.1 or maybe 4.0.1. This was concerning to me for a few reasons. NET Framework, the Entity Framework, SQL Server, and a dozen more. ![]() This post isn't specific to this update, but ALL the updates lately, from the. NET Framework 4 to include new features and functionality around Workflow and Azure. I noticed recently that Microsoft released something called ".NET 4.0 Platform Update 1." This is an update to the. ![]() NET versioning, and see what your thoughts are so that I might share them with TPTB (The Powers That Be). I want to talk to you about some things I've noticed around. Naming Things is Step 0 when it comes to understanding Things. I really care about how products are versioned and I'm sure you to do, Dear Reader. If you do, then I can make sure your voice is heard. What I want to know from you, is DO YOU CARE. This is not intended as a rant or a complaint, although there is frustration on my part. Today I noticed that Microsoft published a patch/update to Entity Framework 4.1 (Code First), a product I personally love and support, and they've called it EF 4.1 Update 1. ![]() I've gotten close to posting it, held back, then gotten close to posting again. NOTE: I have had this blog post sitting in my drafts for a few months now. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |