>>As I just mentioned in a message to Craig that my issue could be that Microsoft ASP.NET Web Optimization Framework is not up-to-date.
>>
>>I go to NuGet packages and see in the Updates branch one of the items:
>>Microsoft ASP.NET Web Optimization Framework
>>
>>In the right panel of the NuGet is says that this package (id: Microsoft.Asp.Net.Web.Optimization) version 1.1.2 is Last Updated: 12/17/2012. Which is today. Strange coincidence.
>>
>>Before I update I would like to learn something. If I wanted to find out the version of Microsoft ASP.NET Web Optimization Framework
>>I have now, how would I go about it?
>>
>>TIA.
>
>I found the answer by going to the Properties of the References -> Microsoft.AspNet.Web.Optimization.WebForms and it shows version 1.0.0.0. So I know that I was the alpha tester <bg>. On to update.
Strange that after I - supposedly - updates the Microsoft.AspNet.Web.Optimization.WebForms, the version in Properties still shows 1.0.0.0.
When I look at the BIN folder of my solution the Microsoft.Asp.Net.Web.Optimization.WebForms.dlll still of older date (10/13/2013).
But the folder MySolution\Packages\ has new folders with the new version number. Do I need to 'manually' move the file from Packages to BIN?
UPDATE. The current .dll points to this folder:
D:\VS2012\WebProjects\MySolution\packages\Microsoft.AspNet.Web.Optimization.WebForms.1.0.0\lib\net45\Microsoft.AspNet.Web.Optimization.WebForms.dll
But the NuGet created folder:
..packages\Microsoft.AspNet.Web.Optimization.1.1.2.lib.net40 where the more up-to-date DLL resides.
I thought that NuGet would update the solution but it didn't
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham