iT Synergy Blogs

Growing Innovation - Soluciones a problemas reales

Copyright © 2026 · iT Synergy·

Visual Studio 2011 as a Windows Phone dev machine

By Leave a Comment

The first thing I noticed after installing the newly distributed Visual Studio 2011 is it does not bring the windows phone SDK pre-packaged as you can see silverlight for windows phone template is not installed there.

image‘

image

image

I tried downloading again the SDK as I have a Visual studio 2010 running on the same machine and probably it was only installed for that particular version.

image

image

To my surprise I noticed it didn’t work as expected and it only refreshed the VS2010 templates for silverlight, I just dug a little bit more and found out the following reference on the official windows blog:

“The Windows Phone SDK and Visual Studio “11” Beta

Many folks have also noticed that the new preview release of next version of Visual Studio (the “Visual Studio 11 Beta”, available here) does not include support for developing Windows Phone applications. Rest assured, there absolutely will be support for building Windows Phone applications with the next version of Visual Studio by the time it RTMs. Prior to that, per the first point above, we will be enabling the Windows Phone SDK 7.1 on Windows 8 in the coming months”

This means we should continue working on Visual studio 2010 for a while when referring to windows phone development. Personally think the new improvements on visual studio 11 are great but this is somehow a step back from a developer-new-technology-penetration-point-of-view, hopefully they will fix this in no time for VS11 and Windows 8

Greetings

By Leave a Comment

hi Guys

my name is Gustavo Echeverry and I will be writing about new and cool technology, I am passionate about technology and cool new challenges so expect a lot of windows 8, azure, WCF and windows phone references over here.

Please let me know if you are having some hard issues with something in particular (Microsoft-related) and maybe a could take a crank a it and help you solve it.

Regards

An application error occurred in Catalog Service Operation [GetIdFromName] Parte 2

By Leave a Comment

Problema

Al tratar de importar un servicio WCF en MSE construido a partir de Web Service Software Factory (WSSF), se me presento el siguiente error:

An application error occurred in Catalog Service Operation [GetIdFromName]. Error Detail [Exception Information Type[MseDataException] Source[Microsoft.ManagedSolutions.Mse.Catalog.Data] Message[Procedure or function ‘GetIDFromName’ expects parameter ‘@EntityName’, which was not supplied.] StackTrace[ at Microsoft.ManagedSolutions.Mse.Catalog.Data.Entity.GetIdFromName(String entityName, EntityClass entityClass, SqlTransaction transaction, SqlConnection connection) at Microsoft.ManagedSolutions.Mse.Catalog.Module.Business.EntityManager.GetIdFromName(String entityName, EntityClass entityClass, SqlTransaction transaction, SqlConnection connection)]Exception Information Type[SqlException] Source[.Net SqlClient Data Provider] Message[Procedure or function ‘GetIDFromName’ expects parameter ‘@EntityName’, which was not supplied.] StackTrace[ at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString) at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result) at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe) at System.Data.SqlClient.SqlCommand.ExecuteNonQuery() at Microsoft.ManagedSolutions.Mse.Catalog.Data.Entity.GetIdFromName(String entityName, EntityClass entityClass, SqlTransaction transaction, SqlConnection connection)]]

Causa

Al parecer el problema es causado por la forma como es serializado el WSDL del servicio.Posibles causas:

  • El modelo de serialización con el que se construyo el servicio WCF con WSSF. Ver la primera parte del blog.
  • No todos los data contract generados estan definidos completamete y más concretamente les hace falta su correspondiente namespace.

Solución

Verificar que en los data contract generados se encuentre establecido el valor XmlRootAttribute con el Namespace correspondiente al contrato, en caso que no lo posea.

Ejemplo,
[System.CodeDom.Compiler.GeneratedCodeAttribute(“System.Xml”, “4.0.30319.233”)]
[System.SerializableAttribute()]
[System.Diagnostics.DebuggerStepThroughAttribute()]
[System.ComponentModel.DesignerCategoryAttribute(“code”)]
[System.Xml.Serialization.XmlTypeAttribute(Namespace=”http://sap.com/xi/FSCM/Global2″)]
[System.Xml.Serialization.XmlRootAttribute(Namespace = “http://sap.com/xi/FSCM/Global2”, IsNullable = true)]
public partial class BusinessScopeID {

Y sabor !!!  Podremos importar el servicio en MSE.