Change Set |
Date |
Downloads |
Comment |
90206
by
furmangg
|
Jun 18 at
11:34 PM
|
29 |
issue 30863: fix for solution folders for Used/Unused Report Datasets feature
|
89886
by
DarrenSQLIS
|
Jun 10 at
1:43 PM
|
17 |
Added VariableEvaluateAsExpressionPractice - Warn when variable has an expression but doesn't have EvaluateAsExpression set.
|
89884
by
DarrenSQLIS
|
Jun 10 at
11:54 AM
|
1 |
Fix for issue 30828 - Variable Copy/Move throws an exception if the package contains a custom tasks which has no icon. Added NoIcon and set it correctly in to ComponentInfo.
|
89863
by
furmangg
|
Jun 9 at
9:37 PM
|
4 |
adding try/catch blocks to Agg Manager to improve error handling
|
89855
by
furmangg
|
Jun 9 at
5:51 PM
|
1 |
fixing issue with losing last character of target server name on Roles Report if the target server is a named instance; issue 30813
|
89788
by
johnwelch
|
Jun 7 at
3:42 PM
|
28 |
|
89566
by
johnwelch
|
Jun 1 at
4:42 PM
|
6 |
Fixes to menu item naming, help links, etc.
|
89562
by
srcurrie
|
Jun 1 at
3:11 PM
|
0 |
1) Fixed line wrapping issue in Overwrite Conflicting Items dialog box label. 2) Final updates to Biml.xsd and BimlEngine.dll.
|
89527
by
srcurrie
|
May 31 at
4:18 PM
|
1 |
Changes to BimlEngine.dll and the consuming interfaces in the Biml plugins to enable multiple Biml files to be error checked or expanded at once.
|
89524
by
johnwelch
|
May 31 at
3:19 PM
|
1 |
1) Changed name of Expand Biml menu item to Generate SSIS Package 2) Updated SortProjectFilesPlugin to match interface. 3) Added DuplicateRoles.cs to SQL2005 project
|
88748
by
DarrenSQLIS
|
May 13 at
10:14 AM
|
14 |
Adding BimlFeaturePluginBase.cs to 2005 project. (VS2005 project ignored as it is already very out of date, should probably remove)
|
88747
by
DarrenSQLIS
|
May 13 at
10:10 AM
|
0 |
Fixed Expression List bug that meant only the first variable with and expression would be found (per container).
|
88745
by
DarrenSQLIS
|
May 13 at
9:48 AM
|
0 |
FriendlyName renamed to FeatureName, which accurately reflects what it is used for. The enable/disable features dialog now only displays unique features (as determined by FeatureName). All plug-ins are enabled and disabled explicitly, the feature roll-up is just within the dialog code, and the associated pseudo property class objects used for the property grid display. Changed BIML plug-in classes to use a common abstract base class that encapsulates the common feature name and description.
|
87433
by
dgosbell
|
Apr 11 at
10:27 AM
|
34 |
Updating Build script and installers to include ExpressionEditor.dll as an external assembly
|
87224
by
srcurrie
|
Apr 6 at
11:05 PM
|
8 |
Rolling back r87187...
I added the #IF KATMAI check because my build machine at the time had a version of SQL Server 2005 that I had freshly installed and not updated with the latest service packs. The property in question was first introduced in SP2. In pre-SP2 versions of BIDS, PC Dim Naturalizer will show a message box with an exception message.
I reviewed this with Greg and we decided to leave the code as was and add a documentation item to note that PC Dim Naturalizer will not work pre-SP2.
|
87187
by
srcurrie
|
Apr 6 at
2:59 AM
|
5 |
Added an #IF KATMAI check around a setter for MemberKeysUnique, because this property was not available in 2005. I suspect someone must have this as a local change, since that property setter was present before the last release.
|
87029
by
srcurrie
|
Apr 3 at
10:05 AM
|
2 |
1) Removed two orphaned assembly references (Microsoft.Data.Schema and Microsoft.Data.Schema.UnitTesting) from SQL2008 project so that TreatWarningsAsErrors would build clean. 2) Fixed an incorrect Xml Doc comment in CustomPropertyDescriptor.cs so that TreatWarningsAsErrors would build clean. 3) Changed Build PowerShell script to reference Properties\AssemblyInfo.cs instead of the now non-existent \assemblyinfo.cs.
Anyone with the proper prereqs installed (SQL Server 2008, SQL Server 2005, NSIS, and NSIS Processes plugin) should now be able to build all distributable packages cleanly from the powershell script.
|
87027
by
srcurrie
|
Apr 3 at
9:33 AM
|
0 |
1) Modified csproj files to include what appear to be necessary property settings but that were missing in the Release configuration. These include TreatWarningsAsErrors, AllowUnsafeBlocks, and DefineConstants 2) Modified the Build powershell script so that it also correctly builds the xcopy deployment zip with the Biml changes.
|
87021
by
srcurrie
|
Apr 3 at
9:16 AM
|
0 |
1) Synchronized SQL2008 and VS2008 project files, so that all Biml changes are reflected in both. 2) Updated VS2008 solution file, which wouldn't open in VS2008 without being upgraded. 3) Small changes to the BimlEngine.dll binary - these mostly focus on modifications to lowering templates to deal with relative paths correctly in the BIDS codegen scenario. 4) Updated installer files for both 2005 and 2008. Both are tested and the generated installers/uninstallers work correctly. 5) Added code to detect the difference between SQL Server 2008 and SQL Server 2008 R2 for code generation. This is done based on inspecting a relevant registry key. 6) Modified BimlValidationListForm so that the column width of description and recommendation have reasonable MaxWidth defaults. 7) Removed a couple of unused System.Linq using statements to enable VS2005 builds.
|
86917
by
srcurrie
|
Apr 1 at
8:06 AM
|
3 |
1) Added check for .NET Framework version with a custom alert dialog box (and convenient download links) 2) Added a MultipleSelectionConfirmationDialog box so that users can select which dtsx packages they wish to overwrite when there are conflicts. 3) Added help buttons to all Biml-related dialog boxes 4) Several small improvements to Biml-related dialog box layout, including start positions and anchoring.
While I will be checking in bug fixes and installer updates soon, the core Biml integration coding work is now complete.
|
86740
by
srcurrie
|
Mar 29 at
8:42 AM
|
3 |
Adding all core functionality for handling Business Intelligence Markup Language (BIML) files in BIDSHelper.
Specifically, the following changes have been made: 1) Project and folder levels have a new context menu item to add a new Biml file, which will be added to Miscellaneous. 2) The context menu for Biml files have 3 new context menu items: a link to documentation, an option to check for errors, and an option to expand the Biml file. 3) Expanding a Biml file will automatically build the resulting packages and add them to your project.
The following items remain to be done: 1) I still need a way to detect the difference between SQL Server 2008 and SQL Server 2008 R2. SSIS codegen is different between these two in a few cases (such as ADO.NET destination). 2) AFAICT, there is no way to add a context menu for the Miscellaneous folder. I'm still looking for a way to do this. 3) I didn’t check in any changes to the installer scripts. I have some local changes, but I’m not confident enough with NSI at this point. The necessary changes include: a. Registering the Biml file extension with our icon b. Copying the 2 additional DLL files to BIDSHelper install directory c. Copying the Biml.xsd file to the default Visual Studio Xml/Schemas directory to enable intellisense. 4) I need to perform additional testing on Visual Studio 2005 – particularly in cases where .NET 3.5 is not installed. 5) We’ll need to update the BimlEngine.dll before shipping with a few final language tweaks that we’re still working on . 6) I have only made changes to the SQL2008_BIDSHelper.csproj for now. I want to be clearer on what the other project files are used for before doing those as well.
|
84632
by
dgosbell
|
Feb 8 at
5:58 AM
|
41 |
Checking in updates to the powershell window plugin, this plugin is not included in the project file as it is still too easy to crash BIDS due to threading issues. It does not appear at this time that it will be possible to resolve this.
|
84631
by
dgosbell
|
Feb 8 at
5:56 AM
|
1 |
Adding SSAS DuplicateRoles plugin
|
80894
by
furmangg
|
Nov 30 2010 at
4:43 AM
|
55 |
beginning work on Denali build
|
78774
by
dgosbell
|
Oct 22 2010 at
9:01 AM
|
41 |
Updating version control bindings
|