Can't install 1.3.1

[ghost]

Can't install 1.3.1 version on Server 2008 R2 SP1 and SQL Server 2008 R2

Error 1001. Unable to get installer types in the c:\Program Files(x86)\PoorMansFormatterSSMSAddIn\PoorManTSqlFormatterSSMSAddIn.dll assembly. -> Unable tp load one or more o fthe requested types. retrieve the LoaderExceptions property for more information.

Screenshot - http://clip2net.com/s/1Hjxp

system has: .NET v2.0.50727 / v3.0 / v3.5 / v4.0.30319

[TaoK]

Hi, thanks for the bug report - can you confirm that you didn't have SSMS open when you were installing the new plugin please? The error above would be consistent with a situation where an older version of the "PoorManTSqlFormatterSSMSAddIn.dll" file was in place and the installer failed to overwrite it... (I would think - I haven't actually seen this happen)

Either way, could you also check whether there is a file at that location, and if so confirm the version number of that file (right-click, properties, in explorer)

Thanks!

[ghost]

It was 1.0.1 version before. Than unistall old version and try to install 1.3.1. "c:\Program Files (x86)\PoorMansTSqlFormatterSSMSAddIn.." is empty http://clip2net.com/s/1HupA Server was Restarted for new MS Updates installed Tnan try to install 1.3.1 version. When I see Error alert? i can see all new files in folder unpacked http://clip2net.com/s/1HusD

But in this time Npp plugin SqlFormatterNppPlugin.1.3.1 works fine in Notepad++ w/o any problems

[ghost]

http://clip2net.com/s/1Huwe this is dll details you also can contact me on skype [ihorlaputin] or ICQ [38766151] and we can use TeamViewer with remote control

[ghost]

additional information: now I have a lot of problems with own local Web Server after Install all new MS Updates ? see the list http://clip2net.com/s/1HBVg closer to error with your AddIn ? I have a problem with part of dll in Bin of my web project? with same error about Assembly http://clip2net.com/s/1HABs for example PDFlib compiled with old itextSharp 4.0.8 now don't works with 5.2.0 in Bin folder. PDFLib and ItextSharp compiled for FW 2.0. Recompiling with new 5.2 for FW3.5-FW4.0 don't remove problem with assembly. Only after recompile PDFLib with new reference on iTextSharp 5.2 and compilling all projects for FW2.0 remove problem with assembly on server

[TaoK]

Ah, that's interesting - sorry I hadn't responded, haven't had time to look and honestly didn't know where to start.

Now that you've pointed out that correllation, I'll try installing the MS updates on laptop and see if I can reproduce.

I should get a chance to try this tomorrow morning.

In the meantime, if you want an earlier release package (see the missing stuff in the changelist), you can access it here: http://www.architectshack.com/GetFile.aspx?Page=PoorMansTSqlFormatter&File=SqlFormatterSSMSAddIn.Setup.1.2.1.msi

[ghost]

with more old version i have error like that http://clip2net.com/s/1HC5Y after updating MS Updates also MS SSQL server - all old version don't works. I try to install 1.2.1 from link and have same problem. This error is issues way I try to install more new version :) Also I can show this http://clip2net.com/s/1HC6C maybe this will help you

[TaoK]

Hi, i've tested this on both Windows 7 and windows 2008 64-bit machines (SQL Server 2008 on one, SQL Server 2008 R2 on the other), with windows updates, no issues.

I have no idea what kind of issue this is, but it seems to somehow be specific to your machine - something wrong with your .Net setup??

I'll try to contact you on skype, see when we could step through things.

[ghost]

UPDATE: 3/20/2012 delivered 2 new hotfixes from MS (look http://clip2net.com/s/1IMhD)

Now on my server works w/o any problem all AddIn versions. Tested 1.2.1 and 1.3.1 .

I think MS delivered hotpatch for error with Assemly

[TaoK]

Hi Ihor,

Thanks for the update - this is even more confusing, because at least one of those (KB2251489) dates back to June of last year... (and the other one dates back to March 12th). You're probably right, they're probably publishing fixes to fixes, but I wish we could get an explanation somewhere :(

Thanks for the update, I'm glad your problem is resolved! (this will also keep my versioning and build process easier than I had feared :) )