0

I have a problem.

I need to upload an .XLS file. After searching for options I found LinqToExce, it seamed great and easy to use but I found two problems.

The first one (maybe because of my ignorance) is the following: Because my application needs to I use log4net version 1.2.15 but LinqToExcel asks for version 1.2.13, I thought I could come to a solution using assemblyBinding in the configuration file but it's not so.

This is the code I added to the config.

<dependentAssembly>
    <assemblyIdentity name="log4net" publicKeyToken="669e0ddf0bb1aa2a" culture="neutral" />
    <bindingRedirect oldVersion="0.0.0.0-1.2.15.0" newVersion="1.2.15.0" />
</dependentAssembly>

I have no problem running the application in my desktop but when I integrate it to the server throws "Not able to load file or assembly 'log4net, Version=1.2.13.0"

I fixed this changing LinqToExcel (its open source) to use log4net 1.2.15.

The second problem is that the web server is 64 bits and even though there is a LinqToExcel 64 bit version available, it requires to enable 32 bits in Application Pools. It works but I don´t know what I am losing, performance?, does this change impact in all the processes of the application?

Well this are the problems I found, if anyone has experience in LinqToExcel and can give a hand I´d be very grateful. I searched for other solutions but I like LinqToExcel much more because its simple and complete. Thanks beforehand.

Greetings.

César

cpistiner
  • 101
  • 3
  • Question 2 answered in http://stackoverflow.com/questions/507820/what-are-the-pros-and-cons-of-running-iis-as-32bit-vs-64bit-on-a-64bit-os Essentially, addressable memory. This isn't a problem in low-scale or web farm environments though. – Paul Bruce Dec 21 '16 at 18:21
  • Thanks @PaulBruce! – cpistiner Dec 22 '16 at 12:05

0 Answers0