-
Debugging a XSL Transform loaded in a project targeting .NET Core 2.2 wouldn't work; just using a csproj targeting .NET Framework with otherwise SAME files worked without problems.
Document Details…
-
```
1) In the Global Settings section there should be a drop down allowing you to
select what xslt transformation one wants to use for a specific mapping.
Selecting automatic will mean that the mapp…
-
```
What steps will reproduce the problem?
1. Generate a .proto file;
2. All types and methods are always public (or protected).
What is the expected output? What do you see instead?
It should be pos…
-
```
What steps will reproduce the problem?
1. Generate a .proto file;
2. All types and methods are always public (or protected).
What is the expected output? What do you see instead?
It should be pos…
-
```
What steps will reproduce the problem?
1. Generate a .proto file;
2. All types and methods are always public (or protected).
What is the expected output? What do you see instead?
It should be pos…
-
```
What steps will reproduce the problem?
1. Generate a .proto file;
2. All types and methods are always public (or protected).
What is the expected output? What do you see instead?
It should be pos…
-
```
What steps will reproduce the problem?
1. Generate a .proto file;
2. All types and methods are always public (or protected).
What is the expected output? What do you see instead?
It should be pos…
-
```
What steps will reproduce the problem?
1. Generate a .proto file;
2. All types and methods are always public (or protected).
What is the expected output? What do you see instead?
It should be pos…
-
```
What steps will reproduce the problem?
1. Generate a .proto file;
2. All types and methods are always public (or protected).
What is the expected output? What do you see instead?
It should be pos…
-
```
What steps will reproduce the problem?
1. Generate a .proto file;
2. All types and methods are always public (or protected).
What is the expected output? What do you see instead?
It should be pos…