locked
Microsoft Platform Test for ISV Solutions (SQL Server component) RRS feed

  • Question

  • I am planning to test against the SQL Server component of the Microsoft Platform Test for ISV Solutions.
    Unfortunately, the Application Test Specification says very little about how the tests are to be conducted, which makes it hard/impossible to pre-test our solution.
    However, the corresponding document for the Microsoft Platform Test for Hosted Solutions does specify some tangible criteria for passing some of the tests.
    Assuming the test procedures are the same, the criteria for passing the SQL Server component using ADO.NET is that ".Net SQL Client Data Provider" is specified as the Application Name in the connection string and visible when running a trace using SQL Server Profiler.

    I claim that this does not make sense. Should it not be considered best practice, or at least be supported, to specify a "real" application name in the connection string?
    Should doing so really cause us to fail the Platform Test? Is this test procedure thought through by Microsoft or did it just seem like an easy way of checking for ADO.NET usage? I didn't even think Microsoft considered .NET FW components to be applications...I don't.
    • Moved by Max Wang_1983 Tuesday, April 26, 2011 5:53 PM forum consolidation (From:Architecture, Tools, and Process for ISVs)
    Monday, January 5, 2009 1:12 PM