SubSonic

Sometimes I'm really glad I have camera on my phone... And yes, those are bike flashers on his belt...

Sometimes I'm really glad I have camera on my phone... And yes, those are bike flashers on his belt...

Support for SQL JOIN syntax is probably our most requested Query feature addition. As you might imagine, fully supporting JOINs while maintaining the simplicity of the SubSonic query syntax is no small chore. Rob and I chatted about this late last ... [More] week, and we both agreed that if SubSonic were to support JOINs, it should do so in a way that makes them easy to work with, and not merely port the SQL syntax into the parser. Personally, I find SQL JOIN syntax convoluted and truly believe that there must a more friendly and readable way to the same ends. In Revision 188, you'll find my first stab at making this happen. First off, a few caveats: The capability is currently supported only on Sql Server Supplementary syntax (WHERE, ORDER BY) etc. are not supported. If they do actually work, it's only out of pure luck LEFT INNER JOIN support only Creating a JOINed Query To facilitate JOIN support, a new Query constructor overload has been added. This overload takes a table schema reference, and one or more table columns as parameters. Query qry = new Query(Product.Schema, Product.ProductIDColumn, Product.ProductNameColumn, Supplier.CompanyNameColumn, Category.CategoryIDColumn);   The column properties represent new static properties in the generated classes, so you'll need to regenerate any existing classes in order to perform these queries. This query syntax ultimately generates the following SQL and result set: SELECT ProductID, ProductName, [J2].[CompanyName], [J3].[CategoryID] FROM [dbo].[Products] INNER JOIN [Suppliers] J2 ON [Products].[SupplierID] = [J2].[SupplierID] INNER JOIN [Categories] J3 ON [Products].[CategoryID] = [J3].[CategoryID]   So consider this just a first pass, with more to come. As always, we welcome any feedback and ideas, so please add your comments! [Less]

Support for SQL JOIN syntax is probably our most requested Query feature addition. As you might imagine, fully supporting JOINs while maintaining the simplicity of the SubSonic query syntax is no small chore. Rob and I chatted about this late last ... [More] week, and we both agreed that if SubSonic were to support JOINs, it should do so in a way that makes them easy to work with, and not merely port the SQL syntax into the parser. Personally, I find SQL JOIN syntax convoluted and truly believe that there must a more friendly and readable way to the same ends. In Revision 188, you'll find my first stab at making this happen. First off, a few caveats: The capability is currently supported only on Sql Server Supplementary syntax (WHERE, ORDER BY) etc. are not supported. If they do actually work, it's only out of pure luck LEFT INNER JOIN support only Creating a JOINed Query To facilitate JOIN support, a new Query constructor overload has been added. This overload takes a table schema reference, and one or more table columns as parameters. Query qry = new Query(Product.Schema, Product.ProductIDColumn, Product.ProductNameColumn, Supplier.CompanyNameColumn, Category.CategoryIDColumn);   The column properties represent new static properties in the generated classes, so you'll need to regenerate any existing classes in order to perform these queries. This query syntax ultimately generates the following SQL and result set: SELECT ProductID, ProductName, [J2].[CompanyName], [J3].[CategoryID] FROM [dbo].[Products] INNER JOIN [Suppliers] J2 ON [Products].[SupplierID] = [J2].[SupplierID] INNER JOIN [Categories] J3 ON [Products].[CategoryID] = [J3].[CategoryID]   So consider this just a first pass, with more to come. As always, we welcome any feedback and ideas, so please add your comments! [Less]

Support for SQL JOIN syntax is probably our most requested Query feature addition. As you might imagine, fully supporting JOINs while maintaining the simplicity of the SubSonic query syntax is no small chore. Rob and I chatted about this late last ... [More] week, and we both agreed that if SubSonic were to support JOINs, it should do so in a way that makes them easy to work with, and not merely port the SQL syntax into the parser. Personally, I find SQL JOIN syntax convoluted and truly believe that there must a more friendly and readable way to the same ends. In Revision 188, you'll find my first stab at making this happen. First off, a few caveats: The capability is currently supported only on Sql Server Supplementary syntax (WHERE, ORDER BY) etc. are not supported. If they do actually work, it's only out of pure luck LEFT INNER JOIN support only Creating a JOINed Query To facilitate JOIN support, a new Query constructor overload has been added. This overload takes a table schema reference, and one or more table columns as parameters. Query qry = new Query(Product.Schema, Product.ProductIDColumn, Product.ProductNameColumn, Supplier.CompanyNameColumn, Category.CategoryIDColumn);   The column properties represent new static properties in the generated classes, so you'll need to regenerate any existing classes in order to perform these queries. This query syntax ultimately generates the following SQL and result set: SELECT ProductID, ProductName, [J2].[CompanyName], [J3].[CategoryID] FROM [dbo].[Products] INNER JOIN [Suppliers] J2 ON [Products].[SupplierID] = [J2].[SupplierID] INNER JOIN [Categories] J3 ON [Products].[CategoryID] = [J3].[CategoryID]   So consider this just a first pass, with more to come. As always, we welcome any feedback and ideas, so please add your comments! [Less]

Support for SQL JOIN syntax is probably our most requested Query feature addition. As you might imagine, fully supporting JOINs while maintaining the simplicity of the SubSonic query syntax is no small chore. Rob and I chatted about this late last ... [More] week, and we both agreed that if SubSonic were to support JOINs, it should do so in a way that makes them easy to work with, and not merely port the SQL syntax into the parser. Personally, I find SQL JOIN syntax convoluted and truly believe that there must a more friendly and readable way to the same ends. In Revision 188, you'll find my first stab at making this happen. First off, a few caveats: The capability is currently supported only on Sql Server Supplementary syntax (WHERE, ORDER BY) etc. are not supported. If they do actually work, it's only out of pure luck LEFT INNER JOIN support only Creating a JOINed Query To facilitate JOIN support, a new Query constructor overload has been added. This overload takes a table schema reference, and one or more table columns as parameters. Query qry = new Query(Product.Schema, Product.ProductIDColumn, Product.ProductNameColumn, Supplier.CompanyNameColumn, Category.CategoryIDColumn); The column properties represent new static properties in the generated classes, so you'll need to regenerate any existing classes in order to perform these queries. This query syntax ultimately generates the following SQL and result set: SELECT ProductID, ProductName, [J2].[CompanyName], [J3].[CategoryID] FROM [dbo].[Products] INNER JOIN [Suppliers] J2 ON [Products].[SupplierID] = [J2].[SupplierID] INNER JOIN [Categories] J3 ON [Products].[CategoryID] = [J3].[CategoryID] So consider this just a first pass, with more to come. As always, we welcome any feedback and ideas, so please add your comments! [Less]

Support for SQL JOIN syntax is probably our most requested Query feature addition. As you might imagine, fully supporting JOINs while maintaining the simplicity of the SubSonic query syntax is no small chore. Rob and I chatted about this late last ... [More] week, and we both agreed that if SubSonic were to support JOINs, it should do so in a way that makes them easy to work with, and not merely port the SQL syntax into the parser. Personally, I find SQL JOIN syntax convoluted and truly believe that there must a more friendly and readable way to the same ends. In Revision 188, you'll find my first stab at making this happen. First off, a few caveats: The capability is currently supported only on Sql Server Supplementary syntax (WHERE, ORDER BY) etc. are not supported. If they do actually work, it's only out of pure luck LEFT INNER JOIN support only Creating a JOINed Query To facilitate JOIN support, a new Query constructor overload has been added. This overload takes a table schema reference, and one or more table columns as parameters. Query qry = new Query(Product.Schema, Product.ProductIDColumn, Product.ProductNameColumn, Supplier.CompanyNameColumn, Category.CategoryIDColumn);   The column properties represent new static properties in the generated classes, so you'll need to regenerate any existing classes in order to perform these queries. This query syntax ultimately generates the following SQL and result set: SELECT ProductID, ProductName, [J2].[CompanyName], [J3].[CategoryID] FROM [dbo].[Products] INNER JOIN [Suppliers] J2 ON [Products].[SupplierID] = [J2].[SupplierID] INNER JOIN [Categories] J3 ON [Products].[CategoryID] = [J3].[CategoryID]   So consider this just a first pass, with more to come. As always, we welcome any feedback and ideas, so please add your comments! [Less]

When I posted my Vista rant a few weeks back, I listed "Mysterious file locking" as one of my gripes. However, a recent discovery has lead to believe that the blame for this issue may not rest solely on Vista. In the interest of full disclosure, I ... [More] should admit that I'm back on Vista (64-bit no less - ouch) for a variety of reasons that I won't go into. Let's just say that I figured every operating system deserves a second chance, and fortunately KB938194 and KB938979 have made the daily grind a little less painful. Does the following scenario sound familiar? You try to delete a folder, but receive a prompt telling you that "access is denied." Setting security permission and taking ownership of the folder does not help. However, if you delete everything inside it the folder first, you can remove it without problem. With a little help from handle.exe, I discovered that in my case the source of the problem was actually TortoiseSVN, or more specifically TSVNCache.exe, which retaining handles on these folders that I was unable to delete. By default, TortoiseSVN will attempt to monitor the status of all directories on all drives, adjusting file and folder icons to reflect that current state of versioned files and folders. However, if you attempt to keep any order to your development projects (or even if you don't) the actual paths on your machine that need to be monitored represent only a subset of the overall directory. This means TortoiseSVN is spending a lot of effort (and disk I/O) watching irrelevant directories. Fortunately, there's a simple way to control this which directories TortoiseSVN will monitor. From the TortoiseSVN help file: "TSVNCache.exe also uses these paths to restrict its scanning. If you want it to look only in particular folders, disable all drive types and include only the folders you specifically want to be scanned." To make this adjustment, simply open up your TortoiseSVN settings (right click on any folder and select TortoiseSVN > Settings) and select Look and Feel > Icon Overlays. Your settings will probably look like the following:  To restrict the monitored paths, uncheck Fixed drives and then use the Exclude paths and Include paths values to narrow the scanning. If the specified directories should be acted on recursively, make sure you add a * to the end of the path. Sure enough, once I made this change, the folder locking problem disappeared. Hooray for small victories! Escape from Hotfix Hell If you ever had to get a hotfix from Microsoft PSS, you know what a time consuming process it can be. You can spend upwards of half an hour on hold before reaching a screener, and subsequently an engineer, both of whom you'll need to convince that you are indeed to experiencing the problem that the hotfix addresses. So needless to say, I was thrilled when I discovered the following page this morning: Hotfix Request Web Submission Form Kudos to Microsoft for finally making it easier to get hotfixes!  [Less]

When I posted my Vista rant a few weeks back, I listed "Mysterious file locking" as one of my gripes. However, a recent discovery has lead to believe that the blame for this issue may not rest solely on Vista. In the interest of full disclosure, I ... [More] should admit that I'm back on Vista (64-bit no less - ouch) for a variety of reasons that I won't go into. Let's just say that I figured every operating system deserves a second chance, and fortunately KB938194 and KB938979 have made the daily grind a little less painful. Does the following scenario sound familiar? You try to delete a folder, but receive a prompt telling you that "access is denied." Setting security permission and taking ownership of the folder does not help. However, if you delete everything inside it the folder first, you can remove it without problem. With a little help from handle.exe, I discovered that in my case the source of the problem was actually TortoiseSVN, or more specifically TSVNCache.exe, which retaining handles on these folders that I was unable to delete. By default, TortoiseSVN will attempt to monitor the status of all directories on all drives, adjusting file and folder icons to reflect that current state of versioned files and folders. However, if you attempt to keep any order to your development projects (or even if you don't) the actual paths on your machine that need to be monitored represent only a subset of the overall directory. This means TortoiseSVN is spending a lot of effort (and disk I/O) watching irrelevant directories. Fortunately, there's a simple way to control this which directories TortoiseSVN will monitor. From the TortoiseSVN help file: "TSVNCache.exe also uses these paths to restrict its scanning. If you want it to look only in particular folders, disable all drive types and include only the folders you specifically want to be scanned." To make this adjustment, simply open up your TortoiseSVN settings (right click on any folder and select TortoiseSVN > Settings) and select Look and Feel > Icon Overlays. Your settings will probably look like the following:  To restrict the monitored paths, uncheck Fixed drives and then use the Exclude paths and Include paths values to narrow the scanning. If the specified directories should be acted on recursively, make sure you add a * to the end of the path. Sure enough, once I made this change, the folder locking problem disappeared. Hooray for small victories! Escape from Hotfix Hell If you ever had to get a hotfix from Microsoft PSS, you know what a time consuming process it can be. You can spend upwards of half an hour on hold before reaching a screener, and subsequently an engineer, both of whom you'll need to convince that you are indeed to experiencing the problem that the hotfix addresses. So needless to say, I was thrilled when I discovered the following page this morning: Hotfix Request Web Submission Form Kudos to Microsoft for finally making it easier to get hotfixes!  [Less]

When I posted my Vista rant a few weeks back, I listed "Mysterious file locking" as one of my gripes. However, a recent discovery has lead to believe that the blame for this issue may not rest solely on Vista. In the interest of full disclosure, I ... [More] should admit that I'm back on Vista (64-bit no less - ouch) for a variety of reasons that I won't go into. Let's just say that I figured every operating system deserves a second chance, and fortunately KB938194 and KB938979 have made the daily grind a little less painful. Does the following scenario sound familiar? You try to delete a folder, but receive a prompt telling you that "access is denied." Setting security permission and taking ownership of the folder does not help. However, if you delete everything inside it the folder first, you can remove it without problem. With a little help from handle.exe, I discovered that in my case the source of the problem was actually TortoiseSVN, or more specifically TSVNCache.exe, which retaining handles on these folders that I was unable to delete. By default, TortoiseSVN will attempt to monitor the status of all directories on all drives, adjusting file and folder icons to reflect that current state of versioned files and folders. However, if you attempt to keep any order to your development projects (or even if you don't) the actual paths on your machine that need to be monitored represent only a subset of the overall directory. This means TortoiseSVN is spending a lot of effort (and disk I/O) watching irrelevant directories. Fortunately, there's a simple way to control this which directories TortoiseSVN will monitor. From the TortoiseSVN help file: "TSVNCache.exe also uses these paths to restrict its scanning. If you want it to look only in particular folders, disable all drive types and include only the folders you specifically want to be scanned." To make this adjustment, simply open up your TortoiseSVN settings (right click on any folder and select TortoiseSVN > Settings) and select Look and Feel > Icon Overlays. Your settings will probably look like the following:  To restrict the monitored paths, uncheck Fixed drives and then use the Exclude paths and Include paths values to narrow the scanning. If the specified directories should be acted on recursively, make sure you add a * to the end of the path. Sure enough, once I made this change, the folder locking problem disappeared. Hooray for small victories! Escape from Hotfix Hell If you ever had to get a hotfix from Microsoft PSS, you know what a time consuming process it can be. You can spend upwards of half an hour on hold before reaching a screener, and subsequently an engineer, both of whom you'll need to convince that you are indeed to experiencing the problem that the hotfix addresses. So needless to say, I was thrilled when I discovered the following page this morning: Hotfix Request Web Submission Form Kudos to Microsoft for finally making it easier to get hotfixes!  [Less]