mujiannan/Analysis-Services
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Update README.md

Browse Source 
Decoupled from VS documentation
This commit is contained in:
Christian Wade 2023-09-29 15:13:45 -07:00 committed by GitHub
parent cdae6b5603
commit 8a44f8cc50
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 8 additions and 33 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

41
AlmToolkit/README.md
View File

@ -1,42 +1,17 @@
### General Usage
For a detailed list of features, see the ALM Toolkit and BISM Normalizer [documentation](https://github.com/microsoft/Analysis-Services/blob/master/AlmToolkit/Model%20Comparison%20and%20Merging%20for%20Analysis%20Services.pdf).
Download from the BISM Normalizer [Visual Studio Marketplace page](https://marketplace.visualstudio.com/items?itemName=ChristianWade.BISMNormalizer3). New releases will be uploaded to this page.
### History & use cases
This video covers BISM Normalizer 3 use cases and demo.
The ALM Toolkit codebase started out as the BISM Normalizer Visual Studio extension. ALM Toolkit is decoupled from Visual Studio.
This video covers BISM Normalizer 3 use cases and demo. The use cases still apply to ALM Toolkit.
[![IMAGE ALT TEXT HERE](http://img.youtube.com/vi/LZdOwfJqFrM/0.jpg)](http://www.youtube.com/watch?v=LZdOwfJqFrM)
### Object Model & Build Process
### Internal code/object model
This video shows the internals of BISM Normalizer 3. Everything still applies except obfuscation, which has been removed.
This video shows the internals and object model of BISM Normalizer/ALM Toolkit. Most of it is still relevant today.
[![IMAGE ALT TEXT HERE](http://img.youtube.com/vi/r3eGK-dSYuw/0.jpg)](http://www.youtube.com/watch?v=r3eGK-dSYuw)
### Command to Perform a Release Build
Output goes to bin\ReleaseObfusc
`msbuild BismNormalizer.csproj /verbosity:m /target:Rebuild /property:Configuration=Release`
### Set Up New Development Machine
VS 2019 Workloads installed must include .NET desktop development and VS extension development.
Requires VS Installer Projects [extension](https://marketplace.visualstudio.com/items?itemName=VisualStudioClient.MicrosoftVisualStudio2017InstallerProjects).
May need to temporarily comment out following at bottom of BismNormalizer.csproj to load project into VS for 1st time. After 1st successful load, add it back.
`Import Project="..\packages\MSBuild.Extension.Pack.1.8.0\build\net40\MSBuild.Extension.Pack.targets"`
Update: 4/23/2018: AMO libraries are now accessed through NuGet references, so no longer necessary to install AMO client libraries from the [MSI](https://docs.microsoft.com/en-us/azure/analysis-services/analysis-services-data-providers).
Do a Release build from the command-line to set up cross project references for the 1st time (see command above) - and then close and reopen VS.
Set AlmToolkit or BismNormalizer as startup project
In BismNormalizer project properities > Debug tab, set
* Start External Program (assuming Enterprise edition): C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\IDE\devenv.exe
* Command Line Arguments: /rootsuffix Exp
The automated tests refer to a localhost SSAS tabular server.