You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Trying to upgrade all the projects from VS2013 to VS2017
We used the Microsoft.WindowsAzure.Storage.v120.v12 to generate the wastorage.lib using VS2013.
Now, when we build Microsoft.WindowsAzure.Storage.v141.sln, the resulted wastorage.lib doesn't contain the API's from the class azure ::storage ::core ::xml ::xml_reader, because WASTORAGE_API is removed from the class declaration.
code in Microsoft.WindowsAzure.Storage.v120.v12
namespace azure { namespace storage { namespace core { namespace xml {
#pragma warning(push)
#pragma warning(disable: 4251)
class WASTORAGE_API xml_reader
{
.....
} code in Microsoft.WindowsAzure.Storage.v141.sln:
namespace azure { namespace storage { namespace core { namespace xml {
class xml_reader
{
.....
}
Any reason, why this class is removed from the exported classes. any alternative classes can be used?
Thanks in advance.
The text was updated successfully, but these errors were encountered:
Trying to upgrade all the projects from VS2013 to VS2017
We used the Microsoft.WindowsAzure.Storage.v120.v12 to generate the wastorage.lib using VS2013.
Now, when we build Microsoft.WindowsAzure.Storage.v141.sln, the resulted wastorage.lib doesn't contain the API's from the class azure ::storage ::core ::xml ::xml_reader, because WASTORAGE_API is removed from the class declaration.
code in Microsoft.WindowsAzure.Storage.v120.v12
namespace azure { namespace storage { namespace core { namespace xml {
#pragma warning(push)
#pragma warning(disable: 4251)
class WASTORAGE_API xml_reader
{
.....
}
code in Microsoft.WindowsAzure.Storage.v141.sln:
namespace azure { namespace storage { namespace core { namespace xml {
class xml_reader
{
.....
}
Any reason, why this class is removed from the exported classes. any alternative classes can be used?
Thanks in advance.
The text was updated successfully, but these errors were encountered: