Skip to content

Commit 876e985

Browse files
mconnewmconnew
authored
Change NetNamedPipe from net6.0-windows to net6.0 in preference to SupportedOSPlatform and throwing if not on Windows (#5112)
1 parent 3cebde0 commit 876e985

23 files changed

+50
-684
lines changed

‎src/System.ServiceModel.NetNamedPipe/src/Resources/strings.resx

Lines changed: 1 addition & 31 deletions
Original file line numberDiff line numberDiff line change
@@ -126,12 +126,6 @@
126126
<data name="ValueMustBeNonNegative" xml:space="preserve">
127127
<value>The value of this argument must be non-negative.</value>
128128
</data>
129-
<data name="SessionValueInvalid" xml:space="preserve">
130-
<value>The Session value '{0}' is invalid. Please specify 'CurrentSession','ServiceSession' or a valid non-negative Windows Session Id.</value>
131-
</data>
132-
<data name="PackageFullNameInvalid" xml:space="preserve">
133-
<value>The package full name '{0}' is invalid.</value>
134-
</data>
135129
<data name="ChannelTypeNotSupported" xml:space="preserve">
136130
<value>The specified channel type {0} is not supported by this channel manager.</value>
137131
</data>
@@ -150,12 +144,6 @@
150144
<data name="PipeEndpointNotFound" xml:space="preserve">
151145
<value>The pipe endpoint '{0}' could not be found on your local machine.</value>
152146
</data>
153-
<data name="SecurityServerTooBusy" xml:space="preserve">
154-
<value>Server '{0}' sent back a fault indicating it is too busy to process the request. Please retry later. Please see the inner exception for fault details.</value>
155-
</data>
156-
<data name="SecurityEndpointNotFound" xml:space="preserve">
157-
<value>Server '{0}' sent back a fault indicating it is in the process of shutting down. Please see the inner exception for fault details.</value>
158-
</data>
159147
<data name="PipeUriSchemeWrong" xml:space="preserve">
160148
<value>URIs used with pipes must use the scheme: 'net.pipe'.</value>
161149
</data>
@@ -198,9 +186,6 @@
198186
<data name="PipeShutdownReadError" xml:space="preserve">
199187
<value>The shutdown indicator was not received from the pipe. The application on the other end of the pipe may not have sent it. The pipe will still be closed.</value>
200188
</data>
201-
<data name="LockTimeoutExceptionMessage" xml:space="preserve">
202-
<value>Cannot claim lock within the allotted timeout of {0}. The time allotted to this operation may have been a portion of a longer timeout.</value>
203-
</data>
204189
<data name="PipeClosed" xml:space="preserve">
205190
<value>The operation cannot be completed because the pipe was closed. This may have been caused by the application on the other end of the pipe exiting.</value>
206191
</data>
@@ -225,22 +210,7 @@
225210
<data name="TraceCodeFailedPipeConnect" xml:space="preserve">
226211
<value>An attempt to connect to the named pipe endpoint at '{1}' failed. Another attempt will be made with {0} remaining in the overall timeout.</value>
227212
</data>
228-
<data name="ActivityBoundary" xml:space="preserve">
229-
<value>Activity boundary</value>
230-
</data>
231-
<data name="InsufficentMemory" xml:space="preserve">
232-
<value>Insufficient memory avaliable to complete the operation.</value>
233-
</data>
234-
<data name="ActivityProcessAction" xml:space="preserve">
235-
<value>Process action '{0}'.</value>
236-
</data>
237-
<data name="CannotDetermineSPNBasedOnAddress" xml:space="preserve">
238-
<value>Client cannot determine the Service Principal Name based on the identity in the target address '{0}' for the purpose of SspiNegotiation/Kerberos. The target address identity must be a UPN identity (like acmedomain\alice) or SPN identity (like host/bobs-machine).</value>
239-
</data>
240-
<data name="ValueMustBePositive" xml:space="preserve">
241-
<value>The value of this argument must be positive.</value>
242-
</data>
243213
<data name="PlatformNotSupported_NetNamedPipe" xml:space="preserve">
244214
<value>NetNamedPipe is not supported on this platform.</value>
245215
</data>
246-
</root>
216+
</root>

‎src/System.ServiceModel.NetNamedPipe/src/Resources/xlf/strings.cs.xlf

Lines changed: 0 additions & 50 deletions
Original file line numberDiff line numberDiff line change
@@ -2,21 +2,6 @@
22
<xliff xmlns="urn:oasis:names:tc:xliff:document:1.2" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="1.2" xsi:schemaLocation="urn:oasis:names:tc:xliff:document:1.2 xliff-core-1.2-transitional.xsd">
33
<file datatype="xml" source-language="en" target-language="cs" original="../strings.resx">
44
<body>
5-
<trans-unit id="ActivityBoundary">
6-
<source>Activity boundary</source>
7-
<target state="translated">Hranice aktivity</target>
8-
<note />
9-
</trans-unit>
10-
<trans-unit id="ActivityProcessAction">
11-
<source>Process action '{0}'.</source>
12-
<target state="translated">Zpracujte akci {0}.</target>
13-
<note />
14-
</trans-unit>
15-
<trans-unit id="CannotDetermineSPNBasedOnAddress">
16-
<source>Client cannot determine the Service Principal Name based on the identity in the target address '{0}' for the purpose of SspiNegotiation/Kerberos. The target address identity must be a UPN identity (like acmedomain\alice) or SPN identity (like host/bobs-machine).</source>
17-
<target state="translated">Klient nemůže určit hlavní název služby (SPN) založený na identitě v cílové adrese {0} pro účel třídy SspiNegotiation nebo protokolu Kerberos. Identitou cílové adresy musí být identita UPN (jako například acmedomain\alice) nebo identita SPN (například host/honzuv-pocitac).</target>
18-
<note />
19-
</trans-unit>
205
<trans-unit id="ChannelTypeNotSupported">
216
<source>The specified channel type {0} is not supported by this channel manager.</source>
227
<target state="translated">Určený typ kanálu {0} není tímto správcem kanálů podporován.</target>
@@ -27,21 +12,6 @@
2712
<target state="translated">Na {0} neposlouchal žádný koncový bod, který by mohl přijmout zprávu. To je často způsobeno nesprávnou adresou nebo akcí SOAP. Další informace zjistíte podle hodnoty vlastnosti InnerException (je-li přítomna).</target>
2813
<note />
2914
</trans-unit>
30-
<trans-unit id="InsufficentMemory">
31-
<source>Insufficient memory avaliable to complete the operation.</source>
32-
<target state="translated">K dokončení operace není dostatek paměti.</target>
33-
<note />
34-
</trans-unit>
35-
<trans-unit id="LockTimeoutExceptionMessage">
36-
<source>Cannot claim lock within the allotted timeout of {0}. The time allotted to this operation may have been a portion of a longer timeout.</source>
37-
<target state="translated">Nelze nárokovat zámek ve vyhrazeném časovém limitu {0}. Čas přidělený této operaci byl pravděpodobně částí delšího časového limitu.</target>
38-
<note />
39-
</trans-unit>
40-
<trans-unit id="PackageFullNameInvalid">
41-
<source>The package full name '{0}' is invalid.</source>
42-
<target state="translated">Úplný název balíčku {0} je neplatný.</target>
43-
<note />
44-
</trans-unit>
4515
<trans-unit id="PipeAlreadyClosing">
4616
<source>The pipe cannot be written to or read from because it is already in the process of being closed.</source>
4717
<target state="translated">Do kanálu nelze zapisovat ani z něj číst, protože již probíhá proces jeho uzavírání.</target>
@@ -172,21 +142,6 @@
172142
<target state="translated">Časový limit větší než hodnota Int32.MaxValue TotalMilliseconds (přibližně 24 dní) nelze akceptovat. Pokud chcete časový limit zakázat, zadejte hodnotu TimeSpan.MaxValue.</target>
173143
<note />
174144
</trans-unit>
175-
<trans-unit id="SecurityEndpointNotFound">
176-
<source>Server '{0}' sent back a fault indicating it is in the process of shutting down. Please see the inner exception for fault details.</source>
177-
<target state="translated">Server {0} odeslal zpět chybu, která udává, že probíhá jeho vypínání. Podrobné informace o chybě naleznete v popisu vnitřní výjimky.</target>
178-
<note />
179-
</trans-unit>
180-
<trans-unit id="SecurityServerTooBusy">
181-
<source>Server '{0}' sent back a fault indicating it is too busy to process the request. Please retry later. Please see the inner exception for fault details.</source>
182-
<target state="translated">Server {0} odeslal zpět chybu, která udává, že je příliš zaneprázdněn a nemůže zpracovat požadavek. Podrobné informace o chybě naleznete v popisu vnitřní výjimky.</target>
183-
<note />
184-
</trans-unit>
185-
<trans-unit id="SessionValueInvalid">
186-
<source>The Session value '{0}' is invalid. Please specify 'CurrentSession','ServiceSession' or a valid non-negative Windows Session Id.</source>
187-
<target state="translated">Hodnota Session {0} je neplatná. Zadejte hodnotu CurrentSession, ServiceSession nebo platnou nezápornou hodnotu Windows Session Id.</target>
188-
<note />
189-
</trans-unit>
190145
<trans-unit id="TraceCodeFailedPipeConnect">
191146
<source>An attempt to connect to the named pipe endpoint at '{1}' failed. Another attempt will be made with {0} remaining in the overall timeout.</source>
192147
<target state="translated">Pokus o připojení ke koncovému bodu pojmenovaného kanálu na {1} se nezdařil. Bude proveden další pokus s celkovým časovým limitem {0}.</target>
@@ -207,11 +162,6 @@
207162
<target state="translated">Hodnota tohoto argumentu nesmí být záporná.</target>
208163
<note />
209164
</trans-unit>
210-
<trans-unit id="ValueMustBePositive">
211-
<source>The value of this argument must be positive.</source>
212-
<target state="translated">Hodnota tohoto argumentu musí být kladná.</target>
213-
<note />
214-
</trans-unit>
215165
</body>
216166
</file>
217167
</xliff>

‎src/System.ServiceModel.NetNamedPipe/src/Resources/xlf/strings.de.xlf

Lines changed: 0 additions & 50 deletions
Original file line numberDiff line numberDiff line change
@@ -2,21 +2,6 @@
22
<xliff xmlns="urn:oasis:names:tc:xliff:document:1.2" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="1.2" xsi:schemaLocation="urn:oasis:names:tc:xliff:document:1.2 xliff-core-1.2-transitional.xsd">
33
<file datatype="xml" source-language="en" target-language="de" original="../strings.resx">
44
<body>
5-
<trans-unit id="ActivityBoundary">
6-
<source>Activity boundary</source>
7-
<target state="translated">Aktivitätsgrenze</target>
8-
<note />
9-
</trans-unit>
10-
<trans-unit id="ActivityProcessAction">
11-
<source>Process action '{0}'.</source>
12-
<target state="translated">Aktion "{0}" verarbeiten.</target>
13-
<note />
14-
</trans-unit>
15-
<trans-unit id="CannotDetermineSPNBasedOnAddress">
16-
<source>Client cannot determine the Service Principal Name based on the identity in the target address '{0}' for the purpose of SspiNegotiation/Kerberos. The target address identity must be a UPN identity (like acmedomain\alice) or SPN identity (like host/bobs-machine).</source>
17-
<target state="translated">Der Client kann den Dienstprinzipalnamen auf der Basis der Identität in der Zieladresse „{0}“ für die Verwendung durch „SspiNegotiation/Kerberos“ nicht bestimmen. Bei der Identität der Zieladresse muss es sich um eine UPN-Identität (wie „acmedomain\alice“) oder SPN-Identität (wie „host/bobs-computer“) handeln.</target>
18-
<note />
19-
</trans-unit>
205
<trans-unit id="ChannelTypeNotSupported">
216
<source>The specified channel type {0} is not supported by this channel manager.</source>
227
<target state="translated">Der angegebene Kanaltyp {0} wird von diesem Kanal-Manager nicht unterstützt.</target>
@@ -27,21 +12,6 @@
2712
<target state="translated">Es war kein an {0} lauschender Endpunkt vorhanden, der die Nachricht akzeptieren konnte. Dies wird häufig durch eine fehlerhafte Adresse oder SOAP-Aktion verursacht. Weitere Details finden Sie unter "InnerException" (sofern vorhanden).</target>
2813
<note />
2914
</trans-unit>
30-
<trans-unit id="InsufficentMemory">
31-
<source>Insufficient memory avaliable to complete the operation.</source>
32-
<target state="translated">Es ist nicht ausreichend Arbeitsspeicher verfügbar, um den Vorgang abzuschließen.</target>
33-
<note />
34-
</trans-unit>
35-
<trans-unit id="LockTimeoutExceptionMessage">
36-
<source>Cannot claim lock within the allotted timeout of {0}. The time allotted to this operation may have been a portion of a longer timeout.</source>
37-
<target state="translated">Die Sperre konnte nicht innerhalb des zugewiesenen Zeitlimits von {0} angefordert werden. Der für diesen Vorgang zugewiesene Zeitraum war möglicherweise ein Teil eines längeren Zeitlimits.</target>
38-
<note />
39-
</trans-unit>
40-
<trans-unit id="PackageFullNameInvalid">
41-
<source>The package full name '{0}' is invalid.</source>
42-
<target state="translated">Der vollständige Paketname '{0}' ist ungültig.</target>
43-
<note />
44-
</trans-unit>
4515
<trans-unit id="PipeAlreadyClosing">
4616
<source>The pipe cannot be written to or read from because it is already in the process of being closed.</source>
4717
<target state="translated">Schreiben in oder Lesen aus der Pipe ist nicht möglich, da die Pipe bereits geschlossen wird.</target>
@@ -172,21 +142,6 @@
172142
<target state="translated">Zeitlimits, die größer als Int32.MaxValue TotalMilliseconds (ca. 24 Tage) sind, können nicht akzeptiert werden. Geben Sie den TimeSpan.MaxValue an, um das Zeitlimit zu deaktivieren.</target>
173143
<note />
174144
</trans-unit>
175-
<trans-unit id="SecurityEndpointNotFound">
176-
<source>Server '{0}' sent back a fault indicating it is in the process of shutting down. Please see the inner exception for fault details.</source>
177-
<target state="translated">Der Server "{0}" hat einen Fehler zurückgesendet, der darauf hinweist, dass der Server gerade heruntergefahren wird. Detaillierte Fehlerinformationen finden Sie in der inneren Ausnahme.</target>
178-
<note />
179-
</trans-unit>
180-
<trans-unit id="SecurityServerTooBusy">
181-
<source>Server '{0}' sent back a fault indicating it is too busy to process the request. Please retry later. Please see the inner exception for fault details.</source>
182-
<target state="translated">Der Server "{0}" hat einen Fehler zurückgesendet, der darauf hinweist, dass er zu ausgelastet ist, um die Anforderung zu verarbeiten. Versuchen Sie es später noch mal. Detaillierte Fehlerinformationen finden Sie in der inneren Ausnahme.</target>
183-
<note />
184-
</trans-unit>
185-
<trans-unit id="SessionValueInvalid">
186-
<source>The Session value '{0}' is invalid. Please specify 'CurrentSession','ServiceSession' or a valid non-negative Windows Session Id.</source>
187-
<target state="translated">Der Session-Wert "{0}" ist ungültig. Geben Sie CurrentSession, ServiceSession oder eine gültige nicht negative Windows-Sitzungs-ID an.</target>
188-
<note />
189-
</trans-unit>
190145
<trans-unit id="TraceCodeFailedPipeConnect">
191146
<source>An attempt to connect to the named pipe endpoint at '{1}' failed. Another attempt will be made with {0} remaining in the overall timeout.</source>
192147
<target state="translated">Fehler beim Versuch, eine Verbindung mit dem Named Pipe-Endpunkt "{1}" herzustellen. Es wird ein weiterer Versuch unternommen. Im Gesamtzeitlimit verbleiben {0}.</target>
@@ -207,11 +162,6 @@
207162
<target state="translated">Der Wert dieses Arguments darf keine negative Zahl sein.</target>
208163
<note />
209164
</trans-unit>
210-
<trans-unit id="ValueMustBePositive">
211-
<source>The value of this argument must be positive.</source>
212-
<target state="translated">Der Wert dieses Arguments muss positiv sein.</target>
213-
<note />
214-
</trans-unit>
215165
</body>
216166
</file>
217167
</xliff>

0 commit comments

Comments
 (0)