Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Start in WebActivator.PostApplicationStartMethod is not working on IIS 6. Is ther any alternate method available #2 #26

Open
appasosawant opened this issue Jan 13, 2015 · 6 comments

Comments

@appasosawant
Copy link

I have working application on local machine. But when i deployed it on SERVER which is having IIS6.0. It is not working. Is there any configuration i need to add?

@appasosawant
Copy link
Author

Im having one dll which is having this start method. And im calling this dll from one MVC application. Also i want to refer same dll in ASP.Net Application

@davidebbo
Copy link
Owner

I haven't used IIS6 in years, but I would have expected this to work fine, unless it's running a very old version of the .NET framework.

@appasosawant
Copy link
Author

I have copied all dlls from local machine to server, but still no luck. Server is having .net 4.0 and IIS6.0.
There is no any entry found in web.config of local for webactivator dll, only reference is added in application, do i need to add any reference in assembly section in compilation tag?

@davidebbo
Copy link
Owner

WebActivator builds on .NET's PreApplicationStartMethodAttribute (docs). It itself has an attribute of the same name, which can be confusing, but it's not the same one.

Anyway, to help isolate, test if the plain PreApplicationStartMethodAttribute works on your server, to keep WebActivator out of the equation.

@appasosawant
Copy link
Author

I have used PreApplicationStartMethodAttribute of System.Web, restarted IIS on server, no luck.

@davidebbo
Copy link
Owner

That's odd. At least it isolates away from WebActivator itself. You may want to ask the non-WebActivator question in a general ASP.NET forum (or StackOverflow).

As a workaround, you can try calling ActivationManager.Run() from your global.asax's Application_Start.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants