But the my Type dropdown dont have "Excluded path", only have "Explicit
Inclusion" and "Wildcard inclusion"
P.S. I am using WSS3 beta 2 TR
"Jason Chan" <n...@email.com> 撰寫於郵件新聞:%23R7AC5M...@TK2MSFTNGP03.phx.gbl...
Sorry,
tk
"Jason Chan" <n...@email.com> wrote in message
news:%233Va$9M9GH...@TK2MSFTNGP02.phx.gbl...
<trust level="Full" originUrl="" />
Here is the error I received:
This control does not allow connection strings with the following
keywords: 'Integrated Security', 'Trusted_Connection'.
Any thoughts?
Todd Klindt [MVP] wrote:
> In v3 things have been rearchitected. You should not have to exclude
> things, as there isn't a SharePoint ISAPI filter ahead of the ASP.net one
> grabbing requests. If your app isn't working I seem to remember you being
> able to set some exclusions in a web.config file, but I'll be damned if I
> can find it right now.
>
> Sorry,
> tk
> "Jason Chan" <n...@email.com> wrote in message
> news:%233Va$9M9GH...@TK2MSFTNGP02.phx.gbl...
> >I follow the instruction there to setup excluded path
> > http://msdn2.microsoft.com/en-us/library/ms433526.aspx
> >
> > But the my Type dropdown dont have "Excluded path", only have "Explicit
> > Inclusion" and "Wildcard inclusion"
> >
> > P.S. I am using WSS3 beta 2 TR
> >
> > "Jason Chan" <n...@email.com>
> > ¼¶¼g©ó¶l¥ó·s»D:%23R7AC5M...@TK2MSFTNGP03.phx.gbl...
tk
"andy" <ahei...@yahoo.com> wrote in message
news:1162484442.5...@m73g2000cwd.googlegroups.com...
I was able to follow the steps, but it looks like it doesn't raise the
trust level, even with this line:
<trust level="Full" originUrl="" />
Here is the error I received:
This control does not allow connection strings with the following
keywords: 'Integrated Security', 'Trusted_Connection'.
Any thoughts?
Todd Klindt [MVP] wrote:
> In v3 things have been rearchitected. You should not have to exclude
> things, as there isn't a SharePoint ISAPI filter ahead of the ASP.net one
> grabbing requests. If your app isn't working I seem to remember you being
> able to set some exclusions in a web.config file, but I'll be damned if I
> can find it right now.
>
> Sorry,
> tk
> "Jason Chan" <n...@email.com> wrote in message
> news:%233Va$9M9GH...@TK2MSFTNGP02.phx.gbl...
> >I follow the instruction there to setup excluded path
> > http://msdn2.microsoft.com/en-us/library/ms433526.aspx
> >
> > But the my Type dropdown dont have "Excluded path", only have "Explicit
> > Inclusion" and "Wildcard inclusion"
> >
> > P.S. I am using WSS3 beta 2 TR
> >
> > "Jason Chan" <n...@email.com>
> > 撰寫於郵件新聞:%23R7AC5M...@TK2MSFTNGP03.phx.gbl...
The web.config for WSS v3 b2tr has the following element:
<tagMapping>
<add tagType="System.Web.UI.WebControls.SqlDataSource,
System.Web, Version=2.0.0.0, Culture=neutral,
PublicKeyToken=b03f5f7f11d50a3a"
mappedTagType="Microsoft.SharePoint.WebControls.SPSqlDataSource,
Microsoft.SharePoint, Version=12.0.0.0, Culture=neutral,
PublicKeyToken=71e9bce111e9429c" />
</tagMapping>
If you use the SQL.DataSource class, you must clear this in the
standalone Asp.net web.config:
<tagMapping>
<clear/>
</tagMapping>
(I'm wondering if you also have to add in the namespace that was
removed in the line before if the standalone application uses web
parts.)
Lastly, I had to add the following httpHanlder into the stand alone
web.config:
<add path="WebResource.axd" verb="GET"
type="System.Web.Handlers.AssemblyResourceLoader" validate="True" />
It threw an error if it wasn't included. I would love to know why its
needed . . .
-- Andy