Druckversion des Themas

Geschrieben von: Estarina 21.05.2014, 19:26

Hallo @ all,

habe vor 1 Stunde folgende Mail erhalten:



-------- Original-Nachricht --------
Betreff: [URGENT ACTION REQUIRED] Critical Defect in PostSharp 3.1: process exits with code -199.
Datum: Wed, 21 May 2014 17:28:11 +0000
Von: Gael Fraiteur <gael@postsharp.net>
An: XXX

PostSharp

Hi [mein Vorname],

We're sorry to announce that a critical defect affects all builds of PostSharp versions 3.1.0-3.1.40 and 3.2.0-3.2.20. We strongly recommend all projects using PostSharp 3.1 to be upgraded to PostSharp 3.1.41.

You will find all the information about the defect here. Below are the details about affected projects and instructions on the action that needs to be taken:

Which projects are affected?

It is important to understand that the defect acts as a “time bomb”. You will be affected by the project even if (a) you did not modify its source code, (b) you did not upgrade PostSharp and © you did not install any Windows update.

Projects that (a) are bound to PostSharp 3.1.0-3.1.33 AND (b) that don’t cause PostSharp to emit an error or warning message are not affected.

ACTION REQUIRED

Upgrade all projects using PostSharp 3.1.0-3.1.40 using NuGet Package Managers:

Open the solution in Visual Studio
Click on menu item Tools / NuGet Package Manager / Manage NuGet Packages for Solutions…
Go to the Update tab
Update all PostSharp packages to v3.1.41 or higher
Deploy the new source code to build server and team members.

Note: Updating the PostSharp Visual Studio Extension (VSiX) is not required and does not solve the issue.

What happens if I don’t upgrade the projects?

If you don’t upgrade the project, the issue may appear later, and your team may lose productivity in diagnosing it.

Does the issue affect run-time behavior of applications built with PostSharp?

No. The defect only affects build-time behavior.

At PostSharp, we are taking our customers’ productivity extremely seriously. We are aware that this issue prevented whole teams of developers from working during several hours, and that the potential impact of the issue may account for dozens of thousands of dollars of combined productivity losses.

Although the defect was caused by a third-party component, we would like to profoundly apologize for the inconveniences caused by the issue.

The complete defect announcement is published here.

Gael Fraiteur | CEO | PostSharp Technologies | CZ: +420 270 007 790 | US: +1 866 576 5361

Facebook Twitter LinkedIn RSS

You are receiving this newsletter because you are registered as a PostSharp user. You may unsubscribe from our mailing list at any time. Our Mailing Address: SharpCrafters s.r.o., Namesti 14 rijna 1307/2, Prague 150 00, Czech Republic


--- NachrichtEnde


Habe auf meinem Rechner nicht PostSharp.


Was hat es mit der Mail auf sich?


Eure Estarina

Geschrieben von: Solution-Design 21.05.2014, 21:40

Das du es entweder doch auf deinem Rechner/PC installiert hast; den Newsletter abonniert hast; etwas getan hast, was du nicht verstanden hast

http://msdn.microsoft.com/de-de/magazine/gg490353.aspx

Geschrieben von: Estarina 22.05.2014, 06:03

Auf dem Dienstrechner kam genau die gleiche Mail - dort läuft auch PostSharp.
Habe gerade mit unseren Programmieren gesprochen, die hatten den Newsletter auch auf die private Mailadressen der Mitarbeiter abonniert - das konnte ja keiner wissen.

O.k. - der Thread hat sich somit erledigt.


Danke Solution-Design.