index > Visual Studio Team System - Architects > Application Diagram doesn't like ATLAS?

Application Diagram doesn't like ATLAS?


Hi folks,

  One of our web developers updated the web.config for our solutions web site program to work with ATLAS. The website runs fine and the ATLAS works, etc. ... but when i've come back into the Application Diagram to double check some stuff, i get this error now :-

Could not load type 'Microsoft.Web.Configuration.MicrosoftWebSectionGroup' from assembly 'System.Web, Version=2.0.0.0, Culture=neutral, PublicKeyTokey=b03f5f7f11d50a3a'.

er.... ?? The Application Digram also stops loading at that point.

When i comment out the SectionGroup and the microsoft.web section in the .config file (the red highlighted stuff), the diagram opens up. Is there something i need to registered with the solution????

Here is the config file btw.

 

Cheers :)

------------

<?xml version="1.0"?>
<!--
    Note: As an alternative to hand editing this file you can use the
    web admin tool to configure settings for your application. Use
    the Website->Asp.Net Configuration option in Visual Studio.
    A full list of settings and comments can be found in
    machine.config.comments usually located in
    \Windows\Microsoft.Net\Framework\v2.x\Config
-->
<configuration>
    <!--
        The configSections define a section for ASP.NET Atlas.
    -->
    <configSections>
        <sectionGroup name="microsoft.web" type="Microsoft.Web.Configuration.MicrosoftWebSectionGroup">
            <section name="converters" type="Microsoft.Web.Configuration.ConvertersSection" requirePermission="false"/>
            <section name="webServices" type="Microsoft.Web.Configuration.WebServicesSection" requirePermission="false"/>
            <section name="authenticationService" type="Microsoft.Web.Configuration.AuthenticationServiceSection" requirePermission="false"/>
            <section name="profileService" type="Microsoft.Web.Configuration.ProfileServiceSection" requirePermission="false"/>
        </sectionGroup>
    </configSections>
    <!--
        The microsoft.web section defines items required for the Atlas framework.
    -->
    <microsoft.web>
        <converters>
            <add type="Microsoft.Web.Script.Serialization.Converters.DataSetConverter"/>
            <add type="Microsoft.Web.Script.Serialization.Converters.DataRowConverter"/>
            <add type="Microsoft.Web.Script.Serialization.Converters.DataTableConverter"/>
        </converters>
        <webServices enableBrowserAccess="true"/>
        <!--
            Uncomment this line to enable the authentication service.
            <authenticationService enabled="true" />
        -->
        <!-- Uncomment these lines to enable the profile service. To allow profile properties to be retrieved
            and modified in Atlas applications, you need to add each property name to the setProperties and
            getProperties attributes.  If you intend for all properties to be available, you can use "*"
            as a shorthand rather than enumerating each property  -->
        <!-- 
            <profileService enabled="true"
                    setProperties="propertyname1;propertyname2"
                    getProperties="propertyname1;propertyname2" />
        -->
    </microsoft.web>

    <appSettings/>
    <connectionStrings/>
    <system.web>
        <pages theme="Default" masterPageFile="~/Default.master">
            <controls>
                <add namespace="Microsoft.Web.UI" assembly="Microsoft.Web.Atlas" tagPrefix="atlas"/>
                <add namespace="Microsoft.Web.UI.Controls" assembly="Microsoft.Web.Atlas" tagPrefix="atlas"/>
                <add namespace="Appian.Controls" tagPrefix="appian" assembly="App_Code"/>
            </controls>
        </pages>
        <xhtmlConformance mode="Strict"/>
        <!--
            Set compilation debug="true" to insert debugging
            symbols into the compiled page. Because this
            affects performance, set this value to true only
            during development.
        -->
        <compilation debug="true">
            <buildProviders>
                <add extension=".asbx" type="Microsoft.Web.Services.BridgeBuildProvider"/>
            </buildProviders>
            <assemblies>
                <add assembly="System.Design, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
                <add assembly="System.Windows.Forms, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
            </assemblies>
        </compilation>
        <!--
            ASMX is mapped to a new handler so that proxy javascripts can also be served.
        -->
        <httpHandlers>
            <remove verb="*" path="*.asmx"/>
            <add verb="*" path="*.asmx" type="Microsoft.Web.Services.ScriptHandlerFactory" validate="false"/>
            <!--
                The MultiRequestHandler enables multiple requests to be handled in one
                roundtrip to the server. Its use requires Full Trust.
            -->
            <add verb="*" path="atlasbatchcall.axd" type="Microsoft.Web.Services.MultiRequestHandler" validate="false"/>
            <add verb="*" path="atlasglob.axd" type="Microsoft.Web.Globalization.GlobalizationHandler" validate="false"/>
            <!--
                The IFrameHandler enables a limited form of cross-domain calls to 'Atlas' web services.
                This should only be enabled if you need this functionality and you're willing to expose
                the data publicly on the Internet.
                To use it, you will also need to add the attribute [WebOperation(true, ResponseFormatMode.Json, true)]
                on the methods that you want to be called cross-domain.
                This attribute is by default on any DataService's GetData method.         
                <add verb="*" path="iframecall.axd" type="Microsoft.Web.Services.IFrameHandler" validate="false"/>
            -->
            <add verb="*" path="*.asbx" type="Microsoft.Web.Services.ScriptHandlerFactory" validate="false"/>
        </httpHandlers>
        <httpModules>
            <add name="ScriptModule" type="Microsoft.Web.Services.ScriptModule"/>
            <add name="BridgeModule" type="Microsoft.Web.Services.BridgeModule"/>
            <add name="WebResourceCompression" type="Microsoft.Web.Services.WebResourceCompressionModule"/>
        </httpModules>
        <!--
            The <authentication> section enables configuration
            of the security authentication mode used by
            ASP.NET to identify an incoming user.
            <authentication mode="Windows"/>
        -->
        <!--
            The <customErrors> section enables configuration
            of what to do if/when an unhandled error occurs
            during the execution of a request. Specifically,
            it enables developers to configure html error pages
            to be displayed in place of a error stack trace.
            <customErrors mode="RemoteOnly" defaultRedirect="GenericErrorPage.htm">
                <error statusCode="403" redirect="NoAccess.htm"/>
                <error statusCode="404" redirect="FileNotFound.htm"/>
            </customErrors>
        -->
    </system.web>
</configuration>




-Pure Krome-
Pure Krome

This is a known issue. The problem is that our code is unable to find the assembly that contains MicrosoftWebSectionGroup. You can work around the problem by doing the following:

1. Close any running instances of Visual Studio.

2. Copy "Program Files\Microsoft ASP.NET\Atlas\v2.0.50727\Atlas\Microsoft.Web.Atlas.dll" to "Program Files\Microsoft Visual Studio 8\Common7\IDE\PrivateAssemblies".

3. Modify your config file to fully qualify the type names, as shown below (note the addition of the assembly name).

<sectionGroup name="microsoft.web" type="Microsoft.Web.Configuration.MicrosoftWebSectionGroup,Microsoft.Web.Atlas">

<section name="converters" type="Microsoft.Web.Configuration.ConvertersSection,Microsoft.Web.Atlas" requirePermission="false"/>

<section name="webServices" type="Microsoft.Web.Configuration.WebServicesSection,Microsoft.Web.Atlas" requirePermission="false"/>

<section name="authenticationService" type="Microsoft.Web.Configuration.AuthenticationServiceSection,Microsoft.Web.Atlas" requirePermission="false"/>

<section name="profileService" type="Microsoft.Web.Configuration.ProfileServiceSection,Microsoft.Web.Atlas" requirePermission="false"/>

</sectionGroup>

4. Restart Visual Studio.

At this point you should be able to open the Application Designer. Please let us know if this doesn't fix your problem.

Thanks,

Ian Bavey

Lead Software Development Engineer

Team Architect

Ian Bavey

Hello Ian,

thank you kindly for your reply. It worked perfectly. I would like to note one minor difference I was required to make to get this working. First of all, i didn't have ATLAS installed on my machine. Therefore, the folder Program Files\Microsoft ASP.NET\Atlas\v2.0.50727\Atlas\ does not exist. The .dll DOES exist in our solution so i was able to copy the .dll (which tfs source safe had retrieved for me at some point) and copy that .dll to the listed directory. Remember, the dll is used by our website only, which was why the website atlas stuff worked fine.

Now that the band-aid solution worked, will this be fixed in the future? Is there anyway the Distributed Diagrams can also reference any website references also? I'm not try to tell anyone how to do their job, just hopeing that issue will not get lost in these forums only.

Thanks again Ian - top stuff :)




-Pure Krome-
Pure Krome

I'm glad the workaround was successful. We're currently tracking the issue and it will be considered for inclusion in a future release.

Ian

Ian Bavey
I get this same error when trying to access files (images, PDFs, etc.) in a virtual directory mapped to a folder outside of the website folder. Does anyone have any segguestions?
shamila

I'm using VS2005 and July Atlas release and have this web service deployed locally;

using System;

using System.Data;

using System.Web;

using System.Web.Services;

using System.Web.Services.Protocols;

using Microsoft.ApplicationBlocks.Data;

[WebService(Namespace = "http://www.microsoft.com/")]

[WebServiceBinding(ConformsTo = WsiProfiles.BasicProfile1_1)]

public class Service : System.Web.Services.WebService

{

public Service () {

//Uncomment the following line if using designed components

//InitializeComponent();

}

[WebMethod]

public string getEmpnoForUser(string user)

{

string constr = "Data Source=SERVER;uid=USER;database=db;Password=password";

string empno = string.Empty;

try

{

string qry = "SELECT distinct emp_no FROM HH_MASTER WHERE rtrim(UserName)='" + user + "'";

empno = Convert.ToString(SqlHelper.ExecuteScalar(constr, CommandType.Text, qry));

}

catch (Exception ex)

{

empno = "(" + ex.ToString() + ")";

}

return empno;

}

}

I made an Atlas Website and tried to add a web reference to the web service listed above and get error

Server Error in '/services/PdiEmpNo' Application.

Configuration Error

bkoski
reply 6

You can use google to search for other answers

 

More Articles

Updated MSDN content for VS Team Edition for Architects - June 20...
Application Designer Error
Wildcard for version type
Modeling .Net Remoting or DCOM
How to design and code in different block.
calling policy from orchestration.
Filing bugs or suggestions on Microsoft Connect
Building Installer: How do I have it prompt to uninstall all file...
application designer - generic application
Sequence\Flow Diagrams in VSTS
Welcome to Bokebb   New Update   Joins the collection  
 

New Articles

Validate Diagram in Logical Datacenter D…
Correct values for Platform property in …
Provider Endpoint on Application Use ver…
how to create package diagram in vs 2005…
Sequence Diagram
Application Diagram: Windows Service
Filing bugs or suggestions on Microsoft …
How can I export an Application Diagram?
Building Installer: How do I have it pro…
Missing Team Explorer button
CustomEndpoint
Hot to fix "A reference to document…
Same-named web service on two applications
[LDD] Import IIS settings does not impor…
N-Tier application in Application Design…

Hot Articles

Referencing SDM documents for shared ser…
reverse engineering
Application Diagram: Windows Service
where do newbies ask questions?
Sequence\Flow Diagrams in VSTS
How Do I Add Class Diagrams to a C++ Pro…
Generating Deployment Report.
SdmC.exe - where is this tool located ?
Cannot open certain files in VEA 2005 su…
Looking for book suggestions
Web services via class library - how to …
VSTS Architects - how can I unit test?
Adaptive Object Modelling
How to iterate through cached objects
How to implement database size constrain…

Recommend Articles

Sequence Diagram
Visio for Enterprise Architects 2005 doe…
Individual Website settings versus Defau…
Availability of Visio for Enterprise Arc…
Looking for book suggestions
Application locked - error creating conf…
Updated MSDN content for VS Team Edition…
Hosting the Designer outside of Visual S…
Application Diagram
Windows Communication Foundation Support
Application Diagram: Windows Service
Default implementation language for dist…
How to iterate through cached objects
VSTS Architect vs. VSTS Developer
Deployment attribute : System Designer