[# VS11] Available installers for Visual Studio 11 Beta (you hurt the eyes of both # METRO)

image

Hi,

In addition to Windows 8 that has been the great novelty of today, those that we are dedicated to the development of applications already have the possibility of downloading the new Visual Studio 11 Beta. Before we proceed to simply note the following

I HOPE YOU LIKE THE METRO INTERFACE, BECAUSE NOW IT REALLY UP IN DREAMS!!!!

Having said that, already can go to the official site of Visual Studio 11downloads,http://www.microsoft.com/visualstudio/11/en-us/downloads. Where we see the web installers of Team Foundation Server and Visual Studio Ultimate.

image

Metro 1

If we instead want the standalone installers (or Satan alone as telling my boss), then select that option and… more metro!

image

Metro 2

And I tell you that you well not, in any option you select > subway > subway > subway > Metro > Metro > Metro > Metro > Sonrisa

image

Come on that before formatting my already viejuno Windows 8 Developer Preview and install the new Windows 8Consumer Preview, I have a little time of download, interface metro of through.

Greetings @ Home

The Bruno

Downloads: http://www.microsoft.com/visualstudio/11/en-us/downloads

[#VS11] Disponibles los instaladores para Visual Studio 11 Beta (te duelen los ojos de tanto #METRO)

image

Buenas,

además de Windows 8 que ha sido la gran novedad del día de hoy, aquellos que nos dedicamos al desarrollo de aplicaciones ya tenemos la posibilidad de descargar el nuevo Visual Studio 11 Beta. Antes de seguir simplemente advertir lo siguiente

¡¡¡ESPERO QUE TE GUSTE LA INTERFAZ METRO, PORQUE AHORA LO VERAS HASTA EN SUEÑOS !!!

Dicho esto, ya podemos ir al sitio oficial de descargas de Visual Studio 11, http://www.microsoft.com/visualstudio/11/en-us/downloads. Donde vemos los web installers de Visual Studio Ultimate y Team Foundation Server.

image

Metro 1

Si en cambio queremos los instaladores standalone (o satán alone como les decía un jefe mío), pues seleccionamos esa opción y … más metro !!!

image

Metro 2

Y ya te digo que no te salvas, en cualquier opción que selecciones >Metro >Metro >Metro >Metro >Metro >Metro >Metro > Sonrisa

image

Vamos que antes de formatear mi ya viejuno Windows 8 Developer Preview e instalar el nuevo Windows 8 Consumer Preview, tengo un tiempito de descarga, interfaz metro de por medio.

Saludos @ Home

El Bruno

   

Descargas: http://www.microsoft.com/visualstudio/11/en-us/downloads

[# TFS2010] HowTo: Configure a Build to publish debug symbols

image47dd1de4

Hi,

I’m going to aim for but I always forget. In this case, my little set of neurons forget it is advisable to take a set of automatic testing with Intellitrace active execution of a build, publish the symbols (symbol data in English) that are related to our Build. For this I simply follow the following steps

1. Create a shared directory where the symbols will be stored. For example //DROPSERVER/Symbols

2 Give Full permissions to the user that runs the Build

3. In the Build definition, select the process and edit the same.

4. In the section "Basic" modify

Index Sources = True

Path to Publish Symbols = Share created for symbols

image

Ready!

Greetings @ Home

The Bruno

Source: http://msdn.microsoft.com/en-us/library/hh190722.aspx

[#TFS2010] HowTo: Configurar una Build para publicar symbols

image47dd1de4

Buenas,

me lo voy a apuntar porque sino siempre me olvido. En este caso, mi escaso set de neuronas se olvidan de que para tener un set de pruebas automáticas con Intellitrace activo en una ejecución de una build, es recomendable publicar los símbolos (symbol data en inglés) que están relacionados con nuestra Build. Para esto simplemente sigo los siguientes pasos

1. Crear un directorio compartido donde se almacenarán los símbolos. Por ejemplo //DROPSERVER/Symbols

2. Dar permisos Full al usuario que ejecuta la Build

3. En la definición de la Build, seleccionar el proceso y editar el mismo.

4. En la sección “Basic” modificar

Index Sources = True

Path to Publish Symbols = Share creado para los símbolos

image

Listo !!!

 

Saludos @ Home

El Bruno

   

Fuente: http://msdn.microsoft.com/en-us/library/hh190722.aspx

[# KINECT] Changes in # KinectSdk from Beta 2 to SDK V1.0 (I)

image47dd1de4

Hi,

before that I remain obsolete and while I still participate in the MVP Summit 2012 but virtually come with some of the changes that we have to take into account if we have applications for Kinect to use the Kinect SDK Beta 2 and thought of migrating to Kinect SDK V1.0.

References

Initially we had a reference to Microsoft.Research.Kinect

image

With the new SDK must resolve the invalid reference and add a new one to Microsoft. Kinect .

image

Sensor initialization

When we used the Beta 2, we had to define the initialization of the sensor using the Initalize() method and at the same time passed you a series of parameters to initialize camera, depth sensor and detection of skeletons.

   1: void InitKinect()

   2: {

   3:     if (Runtime.Kinects.Count == 0)

   4:         return;

   5:     kinect = Runtime.Kinects[0];

   6:     RuntimeOptions = RuntimeOptions.UseDepthAndPlayerIndex | 

   7:         RuntimeOptions.UseSkeletalTracking | 

   8:         RuntimeOptions.UseColor;

   9:     kinect.Initialize(RuntimeOptions);

  10:     kinect.DepthStream.Open(ImageStreamType.Depth, 2, ImageResolution.Resolution320x240,

  11:         RuntimeOptions.HasFlag(RuntimeOptions.UseDepthAndPlayerIndex) || 

  12:         RuntimeOptions.HasFlag(RuntimeOptions.UseSkeletalTracking) ? 

  13:         ImageType.DepthAndPlayerIndex : ImageType.Depth);

  14:     kinect.DepthFrameReady += this.KinectDepthFrameReady;

  15: }

With SDK V1.0 this is much simpler. I believe that the following code, where only Initializes the depth sensor, is declarative enough as to who understand that the important thing is now in line 6.

   1: void MainWindowLoaded(object sender, RoutedEventArgs e)

   2: {

   3:     if (KinectSensor.KinectSensors.Count == 0)

   4:         return;

   5:     this.kinectSensor = KinectSensor.KinectSensors[0];

   6:     this.kinectSensor.DepthStream.Enable();

   7:     this.kinectSensor.Start();

   8:     this.kinectSensor.DepthFrameReady += this.KinectSensorDepthFrameReady;

   9: }

 

If we wanted as well as the depth sensor to activate the camera stream and also the recognition of skeletons, the following code is that we have to use. The lines  6, 7 and 8 are the important ones.

   1: void MainWindowLoaded(object sender, RoutedEventArgs e)

   2: {

   3:     if (KinectSensor.KinectSensors.Count == 0)

   4:         return;

   5:     this.kinectSensor = KinectSensor.KinectSensors[0];

   6:     this.kinectSensor.ColorStream.Enable();

   7:     this.kinectSensor.SkeletonStream.Enable();

   8:     this.kinectSensor.DepthStream.Enable();

   9:     this.kinectSensor.Start();

  10:     this.kinectSensor.DepthFrameReady += this.KinectSensorDepthFrameReady;

  11: }

 

In coming posts other examples about some changes from Beta 2 to the Final SDK.

Greetings @ Home

El Bruno

Download: http://www.microsoft.com/en-us/kinectforwindows/develop/overview.aspx

[#KINECT] Cambios en #KinectSdk desde Beta 2 a SDK V1.0 (I)

image47dd1de4

Buenas,

antes que me queden obsoletos y mientras sigo participando en el MVP Summit 2012 pero de forma virtual, vamos con algunos de los cambios que tenemos que tener en cuenta si tenemos aplicaciones para Kinect que utilicen el Kinect SDK Beta 2 y pensamos en migrarlas a Kinect SDK V1.0.

Referencias

Inicialmente teníamos una referencia a Microsoft.Research.Kinect

image

Con el nuevo SDK tenemos que resolver la referencia inválida y agregar una nueva a Microsoft.Kinect.

image

 

Inicialización del Sensor

Cuando utilizábamos la Beta 2, teníamos que definir la inicialización del sensor utilizando el método Initalize() y al mismo le pasábamos una serie de parámetros para inicializar la cámara, el sensor de profundidad o la detección de skeletons.

   1: void InitKinect()

   2: {

   3:     if (Runtime.Kinects.Count == 0)

   4:         return;

   5:     kinect = Runtime.Kinects[0];

   6:     RuntimeOptions = RuntimeOptions.UseDepthAndPlayerIndex | 

   7:         RuntimeOptions.UseSkeletalTracking | 

   8:         RuntimeOptions.UseColor;

   9:     kinect.Initialize(RuntimeOptions);

  10:     kinect.DepthStream.Open(ImageStreamType.Depth, 2, ImageResolution.Resolution320x240,

  11:         RuntimeOptions.HasFlag(RuntimeOptions.UseDepthAndPlayerIndex) || 

  12:         RuntimeOptions.HasFlag(RuntimeOptions.UseSkeletalTracking) ? 

  13:         ImageType.DepthAndPlayerIndex : ImageType.Depth);

  14:     kinect.DepthFrameReady += this.KinectDepthFrameReady;

  15: }

Con el SDK V1.0 esto es mucho más simple. Creo que el siguiente código, donde solo se inicializa el sensor de profundidad, es lo suficientemente declarativo como para que se entienda que ahora lo importante está en la línea 7.

   1: void MainWindowLoaded(object sender, RoutedEventArgs e)

   2: {

   3:  

   4:     if (KinectSensor.KinectSensors.Count == 0)

   5:         return;

   6:     this.kinectSensor = KinectSensor.KinectSensors[0];

   7:     this.kinectSensor.DepthStream.Enable();

   8:     this.kinectSensor.Start();

   9:     this.kinectSensor.DepthFrameReady += this.KinectSensorDepthFrameReady;

  10: }

Si además del sensor de profundidad quisiésemos activar el stream de la cámara y además el reconocimiento de skeletons, el siguiente código es el que tenemos que utilizar. Las líneas 7, 8l y 9 son las importantes.

   1: void MainWindowLoaded(object sender, RoutedEventArgs e)

   2: {

   3:  

   4:     if (KinectSensor.KinectSensors.Count == 0)

   5:         return;

   6:     this.kinectSensor = KinectSensor.KinectSensors[0];

   7:     this.kinectSensor.ColorStream.Enable();

   8:     this.kinectSensor.SkeletonStream.Enable();

   9:     this.kinectSensor.DepthStream.Enable();

  10:     this.kinectSensor.Start();

  11:     this.kinectSensor.DepthFrameReady += this.KinectSensorDepthFrameReady;

  12: }

 

En próximos posts otros ejemplos sobre algunos cambios desde Beta 2 al SDK Final.

 

Saludos @ Home

El Bruno

   

Download: http://www.microsoft.com/en-us/kinectforwindows/develop/overview.aspx

[# VS2010] On LightSwitch and how works internally with their databases

image47dd1de4

Hi,

Since a couple of days ago I I am giving a bath of Visual Studio LightSwitch. He may like you or not, but to get you out of a tight spot in a fast CRUD generation, as it is quite powerful. However, when you have a computer with more product trial versions that stable versions, you usually find yourself with errors such as the following.

The first thing I found was at the time of launch my LightSwitch application an error related to the version of SQL Server.

   1: Error    67    Sql Server version not supported.
   2: 11.00.1440    C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\LightSwitch\v1.0\Microsoft.LightSwitch.targets

Of course, the express version of Denali I have installed doesn’t like to LightSwitch. So I decided to change it from Visual Studio configuration: "Tools / / Options"and then in the section"Database Tools / / DataConnections". In my case the option that appeared was ". SQLExpress" and that version of SQL is the 11.

image

I changed the value for a 10 version of SQL Express that I have installed in local, but also ran the application. The next thing was to go see the execution target. That had the target path in

C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\LightSwitch\v1.0\Microsoft.LightSwitch.targets)

Because we see that it has the same code inside. I found several things, but what most caught my attention was that always used a property

$(SqlExpressInstanceName)

that it was not declared anywhere.

   1: <!--The Development Database is built in the same location - Bin\Data - for all configurations.-->
   2: <BuildSchema Inputs="@(LightSwitchModel)"
   3:              ProjectPath="$(MSBuildProjectFullPath)"
   4:              OutputDirectory="Bin\Data"
   5:              SqlExpressInstanceName="$(SqlExpressInstanceName)"
   6:              ExternalDataSources="@(ServerExternalDataSources)"/>
   7: <!--The _IntrinsicData connection string should be updated to use the SQL Express Instance Name
   8:     from the LightSwitch Project' Property-->
   9: <UpdateDataSourceSection ConfigFile="$(OutDir)\web.config"
  10:                          Name="_IntrinsicData"
  11:                          Key="Data Source"
  12:                          Value=".\$(SqlExpressInstanceName)"/>

So the next thing was to edit the project of LightSwitch. This value is not configurable through any site, unless you edit the project *.lsproj file and in it you can see something similar to the following:

   1: <PropertyGroup>
   2:   <Configuration Condition=" '$(Configuration)' == '' ">Debug</Configuration>
   3:   <Platform Condition=" '$(Platform)' == '' ">AnyCPU</Platform>
   4:   <SchemaVersion>2.0</SchemaVersion>
   5:   <ProjectGuid>c3800149-599b-4dbc-ba07-190956453c17</ProjectGuid>
   6:   <OutputType>WinEXE</OutputType>
   7:   <CopyBuildOutputToOutputDirectory>false</CopyBuildOutputToOutputDirectory>
   8:   <RootNamespace>Application5</RootNamespace>
   9:   <AssemblyName>Microsoft.LightSwitch.Server.Host</AssemblyName>
  10:   <TargetFrameworkVersion>v4.0</TargetFrameworkVersion>
  11:   <LightSwitchVersion>v1.0</LightSwitchVersion>
  12:   <LightSwitchProjectVersion>v1.0</LightSwitchProjectVersion>
  13:   <Name>Application5</Name>
  14:   <LightSwitchProjectType>LightSwitch</LightSwitchProjectType>
  15:   <GenerateManifests>true</GenerateManifests>
  16:   <SignManifests>false</SignManifests>
  17:   <BaseIntermediateOutputPath>bin</BaseIntermediateOutputPath>
  18:   <ApplicationClientType>Desktop</ApplicationClientType>
  19:   <ApplicationServerType>LocalHost</ApplicationServerType>
  20:   <RequireSecureConnection>true</RequireSecureConnection>
  21:   <AuthenticationType>None</AuthenticationType>
  22:   <ApplicationName>Application5</ApplicationName>
  23:   <AssemblyVersion>1.0.0.0</AssemblyVersion>
  24:   <ServiceDefinitionFile>ServiceDefinition.csdef</ServiceDefinitionFile>
  25:   <ServiceConfigurationFile>ServiceConfiguration.cscfg</ServiceConfigurationFile>
  26:   <SqlExpressInstanceName>.\sqlexpress</SqlExpressInstanceName>
  27: </PropertyGroup>

In my case, I changed the line 26 by the correct value, did a reload of the project and everything worked. But before going a couple of data to take into account

  • When you create a project of LightSwitch always take the value configured in Visual Studio. If you change the settings in Visual Studio, this change is not reflected in the draft.
  • Both Visual Studio LightSwitch tiempre working with a local sql. And this seems a very simple detail makes the name of the instance in the format ". \INSTANCIA" is invalid. Should be only the name of the instance "Instance"

Good to go with the mega project Risa

Greetings @ Here

The Bruno