We've got a VS 2005, .NET 2.0 app, that appears to have a dependency either on ADOMD and/or OLAP. We don't use either of these in our ASP.NET apps, so I've got to find a way of getting them out of the .MSI that we create. (We create a .MSI so that we can
include Crystal Reports 11 Release 2 as a merge module.) Is there a way I can remove the dependency upon ADOMD / OLAP, and if so, how?
You need to change your programe, make sure you haven't reference it ...
That is the hard part. With newer versions of Visual Studio it's easy for me to find all of the references used in a project. With VS 2005, I'm just not sure where they are. I've been spending days trying to find it. Once I do, what assemblies have a
reference to the MSOLAP.DLL? We use Crystal Reports XI Release 2, ADO.NET, Active Directory (to authenticate users).
I just had a thought. Back in the day, when these 2 ASP.NET apps were created, we just started with VS 2005's default Web Application. I think that those type of projects automatically created a SQL Express database as a part of the app, and put it into
the App_Data folder. Could this be what's causing the .MSI to require the SqlRun_Tools.MSI to be on the server? If so, can I just delete that .MDF and .LDF, and that will get rid of the requirement?
I finally found out what the problem was. I needed to install IIS 6.0 compatibility onto the new server. Once I did that, then the error went away. The whole MSOLAP.DLL things was a red herring.
Doctor Who
Marked as answer by Ming Xu - MSFT on May 31, 2012 01:22 PM
DoctorWho
Member
128 Points
274 Posts
How do I remove a dependency from an ASP.NET 2.0 .MSI installation?
May 04, 2012 04:22 PM|LINK
We've got a VS 2005, .NET 2.0 app, that appears to have a dependency either on ADOMD and/or OLAP. We don't use either of these in our ASP.NET apps, so I've got to find a way of getting them out of the .MSI that we create. (We create a .MSI so that we can include Crystal Reports 11 Release 2 as a merge module.) Is there a way I can remove the dependency upon ADOMD / OLAP, and if so, how?
SonicMan
Participant
1472 Points
228 Posts
Re: How do I remove a dependency from an ASP.NET 2.0 .MSI installation?
May 07, 2012 12:21 PM|LINK
Hi
You need to change your programe, make sure you haven't reference it ...
DoctorWho
Member
128 Points
274 Posts
Re: How do I remove a dependency from an ASP.NET 2.0 .MSI installation?
May 07, 2012 03:50 PM|LINK
That is the hard part. With newer versions of Visual Studio it's easy for me to find all of the references used in a project. With VS 2005, I'm just not sure where they are. I've been spending days trying to find it. Once I do, what assemblies have a reference to the MSOLAP.DLL? We use Crystal Reports XI Release 2, ADO.NET, Active Directory (to authenticate users).
DoctorWho
Member
128 Points
274 Posts
Re: How do I remove a dependency from an ASP.NET 2.0 .MSI installation?
May 10, 2012 07:15 PM|LINK
I just had a thought. Back in the day, when these 2 ASP.NET apps were created, we just started with VS 2005's default Web Application. I think that those type of projects automatically created a SQL Express database as a part of the app, and put it into the App_Data folder. Could this be what's causing the .MSI to require the SqlRun_Tools.MSI to be on the server? If so, can I just delete that .MDF and .LDF, and that will get rid of the requirement?
DoctorWho
Member
128 Points
274 Posts
Re: How do I remove a dependency from an ASP.NET 2.0 .MSI installation?
May 15, 2012 04:55 PM|LINK
I finally found out what the problem was. I needed to install IIS 6.0 compatibility onto the new server. Once I did that, then the error went away. The whole MSOLAP.DLL things was a red herring.