Enterprise Services - ASP.Net

  • Thread starter Thread starter Mythran
  • Start date Start date
M

Mythran

Group,

I have an ASP.Net application which contains separate projects in a solution.
Two of the projects (DAL and BLL) include the TransactionAttribute for each class
which, in turn, inherits the ServicedComponent base class, sample definition
below:

<Transaction(TransactionOption.Required)> _
Public Class Category
Inherits ServicedComponent

<AutoComplete()> _
Public Function Fetch() As MyTypedDataSet.MyTypedDataTable
...
End Function
End Class


Now, every time I compile and then view the WebUI project, I get a compile time
error with access denied to one of the libraries. I can get it to work if I go
back to the project, change anything (add space at end of a line) then recompile
and run the project again (By run, I mean refresh Internet Explorer).

I read up on it and checked out Microsoft.com and found that this is by design.
The .Net Framework does not support executing managed COM+ libraries outside of
the GAC.

Fine, dandy....now, for testing and development purposes....how can I get around
the whole registering the libraries into the GAC? I develop locally and deploy
many times to a testing server daily. Having to register and re-register after
every single compile becomes very time consuming... Any ideas?

Also, the self-registration process fails due to invalid security access for the
ASPNET user account. The user doesn't have permission to register the assemblies
in the registry. Fine, but we do not want to change the ASPNET user account and
we do not want to re-register manually. How can I change the ASPNET account
(domain user, not local) so that it has access to the registry keys required for
assembly self-registration for Component Services?

Thank you,

Mythran
 
not sure why you want to incur the com+ overhead in production, but on your
local box, just reference the dlls directly and skip com+

-- bruce (sqlwork.com)
 
bruce barker said:
not sure why you want to incur the com+ overhead in production, but on your
local box, just reference the dlls directly and skip com+

-- bruce (sqlwork.com)
Click to expand...

Well, the component services is required for our transaction processes. To keep
the transaction code to a minimum, we are just using the code shown in the
example. No extra transaction code required (that we know about). This is going
into production Wednesday and we would like to get the answers we need prior to
that day (umm, 2 days).

Thanks again,

Mythran
 
Back
Top