OBIEE Visual Analyzer doesn't seem to recognize my parent/child hierarchy. That same hierarchy works fine when I use the Analysis and Interactive reporting tool. I have a level based hierarchy that works though. Does Visual Analyzer support parent/child hierarchies?
Also, what's the difference between the Visual Analyzer and the Analysis and Interactive Reporting tool? They both appear to do the same thing.
OBIEE Visual Analyzer vs. Analysis and Interactive Reporting
Related
They have a tool to design DSLs: https://www.jetbrains.com/mps/
Is it possible to embed editor from there into my program? Or the only purpose is to use it during development only (to compile from DSL)?
In principal, since the MPS editor is a Java Swing application, it could be embedded, however, the current wiring makes it not a trivial process. It is definitely off the beaten path.
The preferred way to create single-purpose IDEs around your DSLs is to build a standalone IDE, which leverages the IntelliJ platform and bundles the desired DSLs - https://confluence.jetbrains.com/display/MPSD34/Building+standalone+IDEs+for+your+languages
We have a large VS2012 solution (~250 projects) that is 90% C#. 2 of the 3 C++ projects use the 'v110' Platform Toolset. The third has to use the 'v110_xp' toolset for compatibility with a third party library. Our nightly TFS (2012) build is configured with 'Perform Code Analysis' set to Always.
Unfortunately, the v110_xp platform does not support code analysis (MSDN Blog). This results with the following build failure:
Microsoft.Cpp.Win32.v110_xp.targets(28,5): error MSB8026: Static analysis is not supported with the current platform toolset.
Any ideas how we can prevent code analysis from running on this single project without enabling (by default) code analysis for all projects (except the one)?
You should change the build to be "As Configured" and select I your solution which projects to run analytics on and which not.
https://msdn.microsoft.com/en-us/library/dd547175.aspx
Changing the following helped me:
Configuration Properties -> General -> Platform Toolset
Change was from v120_xp to v120
Is is possible to use Dreamweaver to create Typescript? either as an editor or in some fashion to compile?
I don't think you will be able to get the full TypeScript experience in Dreamweaver. The beauty of tools like Visual Studio or Web Storm is that you can design-time support, compilation-time checking and compilation to JavaScript all built in.
I can't find any documentation for the two major things you would need to bring TypeScript support to Dreamweaver:
Language support extensibility (a language definition of some kind)
Running an external application on save (to run the compiler)
You could probably get enough just with language support by running the compiler manually (probably by adding the command to a batch file) - but I cannot find any information on how to add a language to Dreamweaver.
We have to decide which technology to use for our unit testing. Currently we use Visual Studio 2010 and not happy with MSTest that came with that. It is buggy, poor in deployment (E.g the test setting output directory is not recognized correctly), and have several issues when trying to test assemblies in 32bit and 64bit versions. To make matters worst MSTest does not have a good impedance match with our Jenkins build system. We therefore thought of moving into NUnit. However, no one in our team has a good exposure to NUnit. Also,we will be soon moving into Visual Studio 2012.
I need to know the pros and cons of Visual Studio 2012 MSTest vs Nunit latest version. Since most of the articles on stack overflow are related to older versions of VS they are not related to us. I guess Microsoft has improved MSTest a lot since 2010. Please provide an unbiased comparison with detail technical issues you have faced in both technologies (newer versions only)
I'm using both MSTest and NUnit at the moment. IMHO NUnit is still a better solution. If you have Visual Studio 2012 Premium edition then it's actually quite nice, except for the fact that you can't seem to group together tests. I like the fact it's integrated into Visual Studio, but the lack of grouping and the ability to run a subset of tests without manually selecting them is a huge problem.
The coverage analysis is also pretty neat in Premium. It's fast and gives you what you need quickly. It is a Premium feature though.
Since there are still lacking features in MSTest (even removed features since vs2010), I would still recommend using NUnit for unit tests. The benefits include test grouping by namespace, the ability to add test case annotations (running the same test multiple times with different parameters) and it works well with Opencover and Report Generator for coverage analysis. The main cited con is that it's not integrated like MSTest, so it really depends how much that matters to you as to whether or not that is a con.
#Biranchi: It doesn't matter anymore which unit test framework you use in Visual Studio 2012 (and upwards). See my blogpost here, the sequel to the one you refer to. http://blogs.msdn.com/b/visualstudioalm/archive/2012/11/20/part-2-using-traits-with-different-test-frameworks-in-the-unit-test-explorer.aspx
You can even mix and match tests from different frameworks, you can even do that down to the method level !!
This means you can even move legacy code from one to another with no bad sideeffects.
Also see this for how to use Nuget to install the NUnit adapter into the solution, freeing the developer for installing it herself.
http://blogs.msdn.com/b/visualstudioalm/archive/2013/06/11/part-3-unit-testing-with-traits-and-code-coverage-in-visual-studio-2012-using-the-tfs-build-and-the-new-nuget-adapter-approach.aspx
#Sriwantha: MSTest is a simpler framework than NUnit. NUnit (and also XUnit) give you more flexibility, which also leads to less code to write. One example: If you are using categories (and you should), MSTest require a category to decorate every method. NUnit allows you to decorate the class - that will take effect for all the methods in that class. NUnit also allow to you use strongly typed categories
public class Integration : Category {}
This is enough to declare a category that you can use instead of
Category("Integration");
where you risk spelling errors.
NUnit has much better support for data driven tests.
NUnit has also support for theories
to name a few.
VS2012 does allow categorization of tests into groups if you have "Update 1" or later:
http://msdn.microsoft.com/en-us/library/hh270865.aspx#BKMK_Grouping_and_filtering_the_test_list
Have you looked into Traits functionality of VS ?
http://blogs.msdn.com/b/visualstudioalm/archive/2012/11/09/how-to-manage-unit-tests-in-visual-studio-2012-update-1-part-1-using-traits-in-the-unit-test-explorer.aspx
Grouping is much better in mstest (2012 update 1) compared to nunit.
One more thing to add here. It looks like MSTEST engine doesn't work well with TFS Build in certain scenarios. If you are using TFS build, it won't report the skipped tests (marked with Ignore attribute). It will only include Assert.Inconclusive. If that's an issue, you should use NUnit instead of MSTest.
Pretty straightforward question here: I like tools such as FxCop when it comes to scanning assemblies to get better insight into my code, and would like to start doing it on C# 4.0 assemblies. Any out there yet, or should I sit tight for a few more months while it's released and tools are updated?
What about Microsoft StyleCop for Visual Studio 2010?
The VS2010 beta includes a newer version of Code Analysis, which runs FxCop during the build process and displays the output as warnings. See the Code Analysis tab of project properties.
However, it's only available in the Premium and Ultimate editions. (See comparison)
I really wish that Microsoft would include it in the Express Editions and enable it by default for all projects; that might substantially improve beginner code.
The tool NDepend supports C#4, and even now C#5. It integrates inside Visual Studio 2012, 2010 and 2008. Disclaimer: I am one of the developers of the tool
The tool propose many facilities for your need of scanning assemblies to get better insight into my code, like Dependency Graph, Dependency Matrix, Code Metrics, Code Diff capabilities...
If you like FxCop, then you'll find useful the NDepend possibility to write Code Query and Code Rule over LINQ Queries (namely CQLinq). More than 200 CQLinq code queries and rules are proposed by default.
It is easy to write your own ones or customize existing ones. CQLinq queries are compiled and executed instantly and their results are presented in a browsable-friendly way, see the screenshot below:
The SD C# Clone Doctor statically analyzes C# (yes, even version 4.0) source code for duplication.
The CloneDR can be applied to large scale software systems, and typically finds 10-20% duplicated code.
There is a sample clone report at the link.