Remove extraneous restore step

Configuration/src/AspDotNetCore/CloudFoundry/CloudFoundry.feature

@@ -6,7 +6,6 @@ Feature: CloudFoundry Configuration
     @netcoreapp3.1
     @win10-x64
     Scenario: CloudFoundry Configuration for netcoreapp3.1/win10-x64
-        When you run: dotnet restore
         And you run: dotnet publish -f netcoreapp3.1 -r win10-x64
         And you run in the background: cf push -f manifest-windows.yml -p bin/Debug/netcoreapp3.1/win10-x64/publish
         And you wait until CloudFoundry app cloud is started
@@ -16,7 +15,6 @@ Feature: CloudFoundry Configuration
     @netcoreapp3.1
     @ubuntu.16.04-x64
     Scenario: CloudFoundry Configuration for netcoreapp3.1/ubuntu.16.04-x64
-        When you run: dotnet restore
         And you run: dotnet publish -f netcoreapp3.1 -r ubuntu.16.04-x64
         And you run in the background: cf push -f manifest.yml -p bin/Debug/netcoreapp3.1/ubuntu.16.04-x64/publish
         And you wait until CloudFoundry app cloud is started
@@ -26,7 +24,6 @@ Feature: CloudFoundry Configuration
     @netcoreapp2.1
     @win10-x64
     Scenario: CloudFoundry Configuration for netcoreapp2.1/win10-x64
-        When you run: dotnet restore
         And you run: dotnet publish -f netcoreapp2.1 -r win10-x64
         And you run in the background: cf push -f manifest-windows.yml -p bin/Debug/netcoreapp2.1/win10-x64/publish
         And you wait until CloudFoundry app cloud is started
@@ -36,7 +33,6 @@ Feature: CloudFoundry Configuration
     @netcoreapp2.1
     @ubuntu.16.04-x64
     Scenario: CloudFoundry Configuration for netcoreapp2.1/ubuntu.16.04-x64
-        When you run: dotnet restore
         And you run: dotnet publish -f netcoreapp2.1 -r ubuntu.16.04-x64
         And you run in the background: cf push -f manifest.yml -p bin/Debug/netcoreapp2.1/ubuntu.16.04-x64/publish
         And you wait until CloudFoundry app cloud is started
@@ -46,7 +42,6 @@ Feature: CloudFoundry Configuration
     @net461
     @win10-x64
     Scenario: CloudFoundry Configuration for net461/win10-x64
-        When you run: dotnet restore
         And you run: dotnet publish -f net461 -r win10-x64
         And you run in the background: cf push -f manifest-windows.yml -p bin/Debug/net461/win10-x64/publish
         And you wait until CloudFoundry app cloud is started

Configuration/src/AspDotNetCore/Simple/Simple.feature

@@ -11,7 +11,6 @@ Feature: Simple Configuration
         And you run: git -C spring-cloud-config checkout v2.1.4.RELEASE
         And you run in the background: mvn -f spring-cloud-config/spring-cloud-config-server/pom.xml spring-boot:run
         And you wait until process listening on port 8888
-        And you run: dotnet restore
         And you set env var <env_name> to "<env_value>"
         And you run in the background: dotnet run -f netcoreapp3.1
         And you wait until process listening on port 5000
@@ -30,7 +29,6 @@ Feature: Simple Configuration
         And you run: git -C spring-cloud-config checkout v2.1.4.RELEASE
         And you run in the background: mvn -f spring-cloud-config/spring-cloud-config-server/pom.xml spring-boot:run
         And you wait until process listening on port 8888
-        And you run: dotnet restore
         And you set env var <env_name> to "<env_value>"
         And you run in the background: dotnet run -f netcoreapp2.1
         And you wait until process listening on port 5000
@@ -52,7 +50,6 @@ Feature: Simple Configuration
         And you run: git -C spring-cloud-config checkout v2.1.4.RELEASE
         And you run in the background: mvn -f spring-cloud-config/spring-cloud-config-server/pom.xml spring-boot:run
         And you wait until process listening on port 8888
-        And you run: dotnet restore
         And you set env var <env_name> to "<env_value>"
         And you run in the background: dotnet run -f net461
         And you wait until process listening on port 5000

Configuration/src/AspDotNetCore/SimpleCloudFoundry/SimpleCloudFoundry.feature

@@ -9,7 +9,6 @@ Feature: Simple CloudFoundry Configuration
     Scenario: Simple CloudFoundry Configuration for netcoreapp3.1/win10-x64
         When you run: cf create-service p-config-server standard myConfigServer -c ./config-server.json
         And you wait until CloudFoundry service myConfigServer is created
-        And you run: dotnet restore
         And you run: dotnet publish -f netcoreapp3.1 -r win10-x64
         And you run in the background: cf push -f manifest-windows.yml -p bin/Debug/netcoreapp3.1/win10-x64/publish
         And you wait until CloudFoundry app foo is started
@@ -21,7 +20,6 @@ Feature: Simple CloudFoundry Configuration
     Scenario: Simple CloudFoundry Configuration for netcoreapp3.1/ubuntu.16.04-x64
         When you run: cf create-service p-config-server standard myConfigServer -c ./config-server.json
         And you wait until CloudFoundry service myConfigServer is created
-        And you run: dotnet restore
         And you run: dotnet publish -f netcoreapp3.1 -r ubuntu.16.04-x64
         And you run in the background: cf push -f manifest.yml -p bin/Debug/netcoreapp3.1/ubuntu.16.04-x64/publish
         And you wait until CloudFoundry app foo is started
@@ -33,7 +31,6 @@ Feature: Simple CloudFoundry Configuration
     Scenario: Simple CloudFoundry Configuration for netcoreapp2.1/win10-x64
         When you run: cf create-service p-config-server standard myConfigServer -c ./config-server.json
         And you wait until CloudFoundry service myConfigServer is created
-        And you run: dotnet restore
         And you run: dotnet publish -f netcoreapp2.1 -r win10-x64
         And you run in the background: cf push -f manifest-windows.yml -p bin/Debug/netcoreapp2.1/win10-x64/publish
         And you wait until CloudFoundry app foo is started
@@ -45,7 +42,6 @@ Feature: Simple CloudFoundry Configuration
     Scenario: Simple CloudFoundry Configuration for netcoreapp2.1/ubuntu.16.04-x64
         When you run: cf create-service p-config-server standard myConfigServer -c ./config-server.json
         And you wait until CloudFoundry service myConfigServer is created
-        And you run: dotnet restore
         And you run: dotnet publish -f netcoreapp2.1 -r ubuntu.16.04-x64
         And you run in the background: cf push -f manifest.yml -p bin/Debug/netcoreapp2.1/ubuntu.16.04-x64/publish
         And you wait until CloudFoundry app foo is started
@@ -57,7 +53,6 @@ Feature: Simple CloudFoundry Configuration
     Scenario: Simple CloudFoundry Configuration for net461/win10-x64
         When you run: cf create-service p-config-server standard myConfigServer -c ./config-server.json
         And you wait until CloudFoundry service myConfigServer is created
-        And you run: dotnet restore
         And you run: dotnet publish -f net461 -r win10-x64
         And you run in the background: cf push -f manifest-windows.yml -p bin/Debug/net461/win10-x64/publish
         And you wait until CloudFoundry app foo is started

Connectors/src/AspDotNetCore/MySql/MySql.feature

@@ -9,7 +9,6 @@ Feature: MySql Connector
     Scenario: MySql Connector for netcoreapp3.1/win10-x64
         When you run: cf create-service p.mysql db-small myMySqlService
         And you wait until CloudFoundry service myMySqlService is created
-        And you run: dotnet restore
         And you run: dotnet publish -f netcoreapp3.1 -r win10-x64
         And you run in the background: cf push -f manifest-windows.yml -p bin/Debug/netcoreapp3.1/win10-x64/publish
         And you wait until CloudFoundry app mysql-connector is started
@@ -22,7 +21,6 @@ Feature: MySql Connector
     Scenario: MySql Connector for netcoreapp3.1/ubuntu.16.04-x64
         When you run: cf create-service p.mysql db-small myMySqlService
         And you wait until CloudFoundry service myMySqlService is created
-        And you run: dotnet restore
         And you run: dotnet publish -f netcoreapp3.1 -r ubuntu.16.04-x64
         And you run in the background: cf push -f manifest.yml -p bin/Debug/netcoreapp3.1/ubuntu.16.04-x64/publish
         And you wait until CloudFoundry app mysql-connector is started
@@ -35,7 +33,6 @@ Feature: MySql Connector
     Scenario: MySql Connector for netcoreapp2.1/win10-x64
         When you run: cf create-service p.mysql db-small myMySqlService
         And you wait until CloudFoundry service myMySqlService is created
-        And you run: dotnet restore
         And you run: dotnet publish -f netcoreapp2.1 -r win10-x64
         And you run in the background: cf push -f manifest-windows.yml -p bin/Debug/netcoreapp2.1/win10-x64/publish
         And you wait until CloudFoundry app mysql-connector is started
@@ -48,7 +45,6 @@ Feature: MySql Connector
     Scenario: MySql Connector for netcoreapp2.1/ubuntu.16.04-x64
         When you run: cf create-service p.mysql db-small myMySqlService
         And you wait until CloudFoundry service myMySqlService is created
-        And you run: dotnet restore
         And you run: dotnet publish -f netcoreapp2.1 -r ubuntu.16.04-x64
         And you run in the background: cf push -f manifest.yml -p bin/Debug/netcoreapp2.1/ubuntu.16.04-x64/publish
         And you wait until CloudFoundry app mysql-connector is started
@@ -61,7 +57,6 @@ Feature: MySql Connector
     Scenario: MySql Connector for net461/win10-x64
         When you run: cf create-service p.mysql db-small myMySqlService
         And you wait until CloudFoundry service myMySqlService is created
-        And you run: dotnet restore
         And you run: dotnet publish -f net461 -r win10-x64
         And you run in the background: cf push -f manifest-windows.yml -p bin/Debug/net461/win10-x64/publish
         And you wait until CloudFoundry app mysql-connector is started

Connectors/src/AspDotNetCore/MySqlEF6/MySqlEF6.feature

@@ -9,7 +9,6 @@ Feature: MySqlEF6 Connector
     Scenario: MySqlEF6 Connector for net461/win10-x64
         When you run: cf create-service p.mysql db-small myMySqlService
         And you wait until CloudFoundry service myMySqlService is created
-        And you run: dotnet restore
         And you run: dotnet publish -f net461 -r win10-x64
         And you run in the background: cf push -f manifest-windows.yml -p bin/Debug/net461/win10-x64/publish
         And you wait until CloudFoundry app mysqlef6-connector is started

Connectors/src/AspDotNetCore/MySqlEFCore/MySqlEFCore.feature

@@ -9,7 +9,6 @@ Feature: MySqlEFCore Connector
     Scenario: MySqlEFCore Connector for netcoreapp3.1/win10-x64
         When you run: cf create-service p.mysql db-small myMySqlService
         And you wait until CloudFoundry service myMySqlService is created
-        And you run: dotnet restore
         And you run: dotnet publish -f netcoreapp3.1 -r win10-x64
         And you run in the background: cf push -f manifest-windows.yml -p bin/Debug/netcoreapp3.1/win10-x64/publish
         And you wait until CloudFoundry app mysqlefcore-connector is started
@@ -22,7 +21,6 @@ Feature: MySqlEFCore Connector
     Scenario: MySqlEFCore Connector for netcoreapp3.1/ubuntu.16.04-x64
         When you run: cf create-service p.mysql db-small myMySqlService
         And you wait until CloudFoundry service myMySqlService is created
-        And you run: dotnet restore
         And you run: dotnet publish -f netcoreapp3.1 -r ubuntu.16.04-x64
         And you run in the background: cf push -f manifest.yml -p bin/Debug/netcoreapp3.1/ubuntu.16.04-x64/publish
         And you wait until CloudFoundry app mysqlefcore-connector is started
@@ -35,7 +33,6 @@ Feature: MySqlEFCore Connector
     Scenario: MySqlEFCore Connector for netcoreapp2.1/win10-x64
         When you run: cf create-service p.mysql db-small myMySqlService
         And you wait until CloudFoundry service myMySqlService is created
-        And you run: dotnet restore
         And you run: dotnet publish -f netcoreapp2.1 -r win10-x64
         And you run in the background: cf push -f manifest-windows.yml -p bin/Debug/netcoreapp2.1/win10-x64/publish
         And you wait until CloudFoundry app mysqlefcore-connector is started
@@ -48,7 +45,6 @@ Feature: MySqlEFCore Connector
     Scenario: MySqlEFCore Connector for netcoreapp2.1/ubuntu.16.04-x64
         When you run: cf create-service p.mysql db-small myMySqlService
         And you wait until CloudFoundry service myMySqlService is created
-        And you run: dotnet restore
         And you run: dotnet publish -f netcoreapp2.1 -r ubuntu.16.04-x64
         And you run in the background: cf push -f manifest.yml -p bin/Debug/netcoreapp2.1/ubuntu.16.04-x64/publish
         And you wait until CloudFoundry app mysqlefcore-connector is started

Connectors/src/AspDotNetCore/PostgreEFCore/PostgreEFCore.feature

@@ -9,7 +9,6 @@ Feature: PostgreEFCore Connector
     Scenario: PostgreEFCore Connector for netcoreapp3.1/win10-x64
         When you run: cf create-service postgresql-10-odb standalone myPostgres -c '{"db_name":"postgresample", "db_username":"steeltoe", "owner_name":"Steeltoe Demo", "owner_email":"demo@steeltoe.io"}'
         And you wait until CloudFoundry service myPostgres is created
-        And you run: dotnet restore
         And you run: dotnet publish -f netcoreapp3.1 -r win10-x64
         And you run in the background: cf push -f manifest-windows.yml -p bin/Debug/netcoreapp3.1/win10-x64/publish
         And you wait until CloudFoundry app postgresefcore-connector is started
@@ -22,7 +21,6 @@ Feature: PostgreEFCore Connector
     Scenario: PostgreEFCore Connector for netcoreapp3.1/ubuntu.16.04-x64
         When you run: cf create-service postgresql-10-odb standalone myPostgres -c '{"db_name":"postgresample", "db_username":"steeltoe", "owner_name":"Steeltoe Demo", "owner_email":"demo@steeltoe.io"}'
         And you wait until CloudFoundry service myPostgres is created
-        And you run: dotnet restore
         And you run: dotnet publish -f netcoreapp3.1 -r ubuntu.16.04-x64
         And you run in the background: cf push -f manifest.yml -p bin/Debug/netcoreapp3.1/ubuntu.16.04-x64/publish
         And you wait until CloudFoundry app postgresefcore-connector is started
@@ -35,7 +33,6 @@ Feature: PostgreEFCore Connector
     Scenario: PostgreEFCore Connector for netcoreapp2.1/win10-x64
         When you run: cf create-service postgresql-10-odb standalone myPostgres -c '{"db_name":"postgresample", "db_username":"steeltoe", "owner_name":"Steeltoe Demo", "owner_email":"demo@steeltoe.io"}'
         And you wait until CloudFoundry service myPostgres is created
-        And you run: dotnet restore
         And you run: dotnet publish -f netcoreapp2.1 -r win10-x64
         And you run in the background: cf push -f manifest-windows.yml -p bin/Debug/netcoreapp2.1/win10-x64/publish
         And you wait until CloudFoundry app postgresefcore-connector is started
@@ -48,7 +45,6 @@ Feature: PostgreEFCore Connector
     Scenario: PostgreEFCore Connector for netcoreapp2.1/ubuntu.16.04-x64
         When you run: cf create-service postgresql-10-odb standalone myPostgres -c '{"db_name":"postgresample", "db_username":"steeltoe", "owner_name":"Steeltoe Demo", "owner_email":"demo@steeltoe.io"}'
         And you wait until CloudFoundry service myPostgres is created
-        And you run: dotnet restore
         And you run: dotnet publish -f netcoreapp2.1 -r ubuntu.16.04-x64
         And you run in the background: cf push -f manifest.yml -p bin/Debug/netcoreapp2.1/ubuntu.16.04-x64/publish
         And you wait until CloudFoundry app postgresefcore-connector is started

Connectors/src/AspDotNetCore/PostgreSql/PostgreSql.feature

@@ -9,7 +9,6 @@ Feature: PostgreSql Connector
     Scenario: PostgreSql Connector for netcoreapp3.1/win10-x64
         When you run: cf create-service postgresql-10-odb standalone myPostgres -c '{"db_name":"postgresample", "db_username":"steeltoe", "owner_name":"Steeltoe Demo", "owner_email":"demo@steeltoe.io"}'
         And you wait until CloudFoundry service myPostgres is created
-        And you run: dotnet restore
         And you run: dotnet publish -f netcoreapp3.1 -r win10-x64
         And you run in the background: cf push -f manifest-windows.yml -p bin/Debug/netcoreapp3.1/win10-x64/publish
         And you wait until CloudFoundry app postgres-connector is started
@@ -22,7 +21,6 @@ Feature: PostgreSql Connector
     Scenario: PostgreSql Connector for netcoreapp3.1/ubuntu.16.04-x64
         When you run: cf create-service postgresql-10-odb standalone myPostgres -c '{"db_name":"postgresample", "db_username":"steeltoe", "owner_name":"Steeltoe Demo", "owner_email":"demo@steeltoe.io"}'
         And you wait until CloudFoundry service myPostgres is created
-        And you run: dotnet restore
         And you run: dotnet publish -f netcoreapp3.1 -r ubuntu.16.04-x64
         And you run in the background: cf push -f manifest.yml -p bin/Debug/netcoreapp3.1/ubuntu.16.04-x64/publish
         And you wait until CloudFoundry app postgres-connector is started
@@ -35,7 +33,6 @@ Feature: PostgreSql Connector
     Scenario: PostgreSql Connector for netcoreapp2.1/win10-x64
         When you run: cf create-service postgresql-10-odb standalone myPostgres -c '{"db_name":"postgresample", "db_username":"steeltoe", "owner_name":"Steeltoe Demo", "owner_email":"demo@steeltoe.io"}'
         And you wait until CloudFoundry service myPostgres is created
-        And you run: dotnet restore
         And you run: dotnet publish -f netcoreapp2.1 -r win10-x64
         And you run in the background: cf push -f manifest-windows.yml -p bin/Debug/netcoreapp2.1/win10-x64/publish
         And you wait until CloudFoundry app postgres-connector is started
@@ -48,7 +45,6 @@ Feature: PostgreSql Connector
     Scenario: PostgreSql Connector for netcoreapp2.1/ubuntu.16.04-x64
         When you run: cf create-service postgresql-10-odb standalone myPostgres -c '{"db_name":"postgresample", "db_username":"steeltoe", "owner_name":"Steeltoe Demo", "owner_email":"demo@steeltoe.io"}'
         And you wait until CloudFoundry service myPostgres is created
-        And you run: dotnet restore
         And you run: dotnet publish -f netcoreapp2.1 -r ubuntu.16.04-x64
         And you run in the background: cf push -f manifest.yml -p bin/Debug/netcoreapp2.1/ubuntu.16.04-x64/publish
         And you wait until CloudFoundry app postgres-connector is started
@@ -61,7 +57,6 @@ Feature: PostgreSql Connector
     Scenario: PostgreSql Connector for net461/win10-x64
         When you run: cf create-service postgresql-10-odb standalone myPostgres -c '{"db_name":"postgresample", "db_username":"steeltoe", "owner_name":"Steeltoe Demo", "owner_email":"demo@steeltoe.io"}'
         And you wait until CloudFoundry service myPostgres is created
-        And you run: dotnet restore
         And you run: dotnet publish -f net461 -r win10-x64
         And you run in the background: cf push -f manifest-windows.yml -p bin/Debug/net461/win10-x64/publish
         And you wait until CloudFoundry app postgres-connector is started

Connectors/src/AspDotNetCore/RabbitMQ/RabbitMQ.feature

@@ -9,7 +9,6 @@ Feature: RabbitMQ Connector
     Scenario: Rabbit Connector for netcoreapp3.1/win10-x64
         When you run: cf create-service p-rabbitmq standard myRabbitMQService
         And you wait until CloudFoundry service myRabbitMQService is created
-        And you run: dotnet restore
         And you run: dotnet publish -f netcoreapp3.1 -r win10-x64
         And you run in the background: cf push -f manifest-windows.yml -p bin/Debug/netcoreapp3.1/win10-x64/publish
         And you wait until CloudFoundry app rabbitmq-connector is started
@@ -22,7 +21,6 @@ Feature: RabbitMQ Connector
     Scenario: Rabbit Connector for netcoreapp3.1/ubuntu.16.04-x64
         When you run: cf create-service p-rabbitmq standard myRabbitMQService
         And you wait until CloudFoundry service myRabbitMQService is created
-        And you run: dotnet restore
         And you run: dotnet publish -f netcoreapp3.1 -r ubuntu.16.04-x64
         And you run in the background: cf push -f manifest.yml -p bin/Debug/netcoreapp3.1/ubuntu.16.04-x64/publish
         And you wait until CloudFoundry app rabbitmq-connector is started
@@ -35,7 +33,6 @@ Feature: RabbitMQ Connector
     Scenario: Rabbit Connector for netcoreapp2.1/win10-x64
         When you run: cf create-service p-rabbitmq standard myRabbitMQService
         And you wait until CloudFoundry service myRabbitMQService is created
-        And you run: dotnet restore
         And you run: dotnet publish -f netcoreapp2.1 -r win10-x64
         And you run in the background: cf push -f manifest-windows.yml -p bin/Debug/netcoreapp2.1/win10-x64/publish
         And you wait until CloudFoundry app rabbitmq-connector is started
@@ -48,7 +45,6 @@ Feature: RabbitMQ Connector
     Scenario: Rabbit Connector for netcoreapp2.1/ubuntu.16.04-x64
         When you run: cf create-service p-rabbitmq standard myRabbitMQService
         And you wait until CloudFoundry service myRabbitMQService is created
-        And you run: dotnet restore
         And you run: dotnet publish -f netcoreapp2.1 -r ubuntu.16.04-x64
         And you run in the background: cf push -f manifest.yml -p bin/Debug/netcoreapp2.1/ubuntu.16.04-x64/publish
         And you wait until CloudFoundry app rabbitmq-connector is started
@@ -61,7 +57,6 @@ Feature: RabbitMQ Connector
     Scenario: Rabbit Connector for net461/win10-x64
         When you run: cf create-service p-rabbitmq standard myRabbitMQService
         And you wait until CloudFoundry service myRabbitMQService is created
-        And you run: dotnet restore
         And you run: dotnet publish -f net461 -r win10-x64
         And you run in the background: cf push -f manifest-windows.yml -p bin/Debug/net461/win10-x64/publish
         And you wait until CloudFoundry app rabbitmq-connector is started

Connectors/src/AspDotNetCore/Redis/Redis.feature

@@ -9,7 +9,6 @@ Feature: Redis Connector
     Scenario: Redis Connector for netcoreapp3.1/win10-x64
         When you run: cf create-service p-redis shared-vm myRedisService
         And you wait until CloudFoundry service myRedisService is created
-        And you run: dotnet restore
         And you run: dotnet publish -f netcoreapp3.1 -r win10-x64
         And you run in the background: cf push -f manifest-windows.yml -p bin/Debug/netcoreapp3.1/win10-x64/publish
         And you wait until CloudFoundry app redis-connector is started
@@ -22,7 +21,6 @@ Feature: Redis Connector
     Scenario: Redis Connector for netcoreapp3.1/ubuntu.16.04-x64
         When you run: cf create-service p-redis shared-vm myRedisService
         And you wait until CloudFoundry service myRedisService is created
-        And you run: dotnet restore
         And you run: dotnet publish -f netcoreapp3.1 -r ubuntu.16.04-x64
         And you run in the background: cf push -f manifest.yml -p bin/Debug/netcoreapp3.1/ubuntu.16.04-x64/publish
         And you wait until CloudFoundry app redis-connector is started
@@ -35,7 +33,6 @@ Feature: Redis Connector
     Scenario: Redis Connector for netcoreapp2.1/win10-x64
         When you run: cf create-service p-redis shared-vm myRedisService
         And you wait until CloudFoundry service myRedisService is created
-        And you run: dotnet restore
         And you run: dotnet publish -f netcoreapp2.1 -r win10-x64
         And you run in the background: cf push -f manifest-windows.yml -p bin/Debug/netcoreapp2.1/win10-x64/publish
         And you wait until CloudFoundry app redis-connector is started
@@ -48,7 +45,6 @@ Feature: Redis Connector
     Scenario: Redis Connector for netcoreapp2.1/ubuntu.16.04-x64
         When you run: cf create-service p-redis shared-vm myRedisService
         And you wait until CloudFoundry service myRedisService is created
-        And you run: dotnet restore
         And you run: dotnet publish -f netcoreapp2.1 -r ubuntu.16.04-x64
         And you run in the background: cf push -f manifest.yml -p bin/Debug/netcoreapp2.1/ubuntu.16.04-x64/publish
         And you wait until CloudFoundry app redis-connector is started
@@ -61,7 +57,6 @@ Feature: Redis Connector
     Scenario: Redis Connector for net461/win10-x64
         When you run: cf create-service p-redis shared-vm myRedisService
         And you wait until CloudFoundry service myRedisService is created
-        And you run: dotnet restore
         And you run: dotnet publish -f net461 -r win10-x64
         And you run in the background: cf push -f manifest-windows.yml -p bin/Debug/net461/win10-x64/publish
         And you wait until CloudFoundry app redis-connector is started

Management/src/AspDotNetCore/CloudFoundry/CloudFoundry.feature

@@ -9,7 +9,6 @@ Feature: Cloud Foundry Samples
     Scenario: CloudFoundry Management for netcoreapp3.1/win10-x64
         When you run: cf create-service p.mysql db-small myMySqlService
         And you wait until CloudFoundry service myMySqlService is created
-        And you run: dotnet restore
         And you run: dotnet publish -f netcoreapp3.1 -r win10-x64
         And you run in the background: cf push -f manifest-windows.yml -p bin/Debug/netcoreapp3.1/win10-x64/publish
         And you wait until CloudFoundry app actuator is started
@@ -20,7 +19,6 @@ Feature: Cloud Foundry Samples
     Scenario: CloudFoundry Management for netcoreapp3.1/ubuntu.16.04-x64
         When you run: cf create-service p.mysql db-small myMySqlService
         And you wait until CloudFoundry service myMySqlService is created
-        And you run: dotnet restore
         And you run: dotnet publish -f netcoreapp3.1 -r ubuntu.16.04-x64
         And you run in the background: cf push -f manifest.yml -p bin/Debug/netcoreapp3.1/ubuntu.16.04-x64/publish
         And you wait until CloudFoundry app actuator is started
@@ -31,7 +29,6 @@ Feature: Cloud Foundry Samples
     Scenario: CloudFoundry Management for netcoreapp2.1/win10-x64
         When you run: cf create-service p.mysql db-small myMySqlService
         And you wait until CloudFoundry service myMySqlService is created
-        And you run: dotnet restore
         And you run: dotnet publish -f netcoreapp2.1 -r win10-x64
         And you run in the background: cf push -f manifest-windows.yml -p bin/Debug/netcoreapp2.1/win10-x64/publish
         And you wait until CloudFoundry app actuator is started
@@ -42,7 +39,6 @@ Feature: Cloud Foundry Samples
     Scenario: CloudFoundry Management for netcoreapp2.1/ubuntu.16.04-x64
         When you run: cf create-service p.mysql db-small myMySqlService
         And you wait until CloudFoundry service myMySqlService is created
-        And you run: dotnet restore
         And you run: dotnet publish -f netcoreapp2.1 -r ubuntu.16.04-x64
         And you run in the background: cf push -f manifest.yml -p bin/Debug/netcoreapp2.1/ubuntu.16.04-x64/publish
         And you wait until CloudFoundry app actuator is started
@@ -53,7 +49,6 @@ Feature: Cloud Foundry Samples
     Scenario: CloudFoundry Management for net461/win10-x64
         When you run: cf create-service p.mysql db-small myMySqlService
         And you wait until CloudFoundry service myMySqlService is created
-        And you run: dotnet restore
         And you run: dotnet publish -f net461 -r win10-x64
         And you run in the background: cf push -f manifest-windows.yml -p bin/Debug/net461/win10-x64/publish
         And you wait until CloudFoundry app actuator is started

Security/src/AspDotNetCore/CloudFoundrySingleSignon/CloudFoundrySingleSignon.feature

@@ -22,7 +22,6 @@ Feature: CloudFoundry Single SignOn
         And you run: uaac client add myTestApp --scope cloud_controller.read,cloud_controller_service_permissions.read,openid,testgroup --authorized_grant_types authorization_code,refresh_token --authorities uaa.resource --redirect_uri https://single-signon.x.y.z/signin-cloudfoundry --autoapprove cloud_controller.read,cloud_controller_service_permissions.read,openid,testgroup --secret myTestApp
         And you run: cf cups myOAuthService -p "{\"client_id\": \"myTestApp\", \"client_secret\": \"myTestApp\", \"uri\": \"uaa://uaa.x.y.z\"}"
         # deploy single-signon app
-        And you run: dotnet restore
         And you run: dotnet publish -f netcoreapp3.1 -r win10-x64
         And you run in the background: cf push -f manifest-windows.yml -p bin/Debug/netcoreapp3.1/win10-x64/publish
         And you wait until CloudFoundry app single-signon is started
@@ -55,7 +54,6 @@ Feature: CloudFoundry Single SignOn
         And you run: uaac client add myTestApp --scope cloud_controller.read,cloud_controller_service_permissions.read,openid,testgroup --authorized_grant_types authorization_code,refresh_token --authorities uaa.resource --redirect_uri https://single-signon.x.y.z/signin-cloudfoundry --autoapprove cloud_controller.read,cloud_controller_service_permissions.read,openid,testgroup --secret myTestApp
         And you run: cf cups myOAuthService -p "{\"client_id\": \"myTestApp\", \"client_secret\": \"myTestApp\", \"uri\": \"uaa://uaa.x.y.z\"}"
         # deploy single-signon app
-        And you run: dotnet restore
         And you run: dotnet publish -f netcoreapp3.1 -r ubuntu.16.04-x64
         And you run in the background: cf push -f manifest.yml -p bin/Debug/netcoreapp3.1/ubuntu.16.04-x64/publish
         And you wait until CloudFoundry app single-signon is started
@@ -88,7 +86,6 @@ Feature: CloudFoundry Single SignOn
         And you run: uaac client add myTestApp --scope cloud_controller.read,cloud_controller_service_permissions.read,openid,testgroup --authorized_grant_types authorization_code,refresh_token --authorities uaa.resource --redirect_uri https://single-signon.x.y.z/signin-cloudfoundry --autoapprove cloud_controller.read,cloud_controller_service_permissions.read,openid,testgroup --secret myTestApp
         And you run: cf cups myOAuthService -p "{\"client_id\": \"myTestApp\", \"client_secret\": \"myTestApp\", \"uri\": \"uaa://uaa.x.y.z\"}"
         # deploy single-signon app
-        And you run: dotnet restore
         And you run: dotnet publish -f netcoreapp2.1 -r win10-x64
         And you run in the background: cf push -f manifest-windows.yml -p bin/Debug/netcoreapp2.1/win10-x64/publish
         And you wait until CloudFoundry app single-signon is started
@@ -122,7 +119,6 @@ Feature: CloudFoundry Single SignOn
         And you run: uaac client add myTestApp --scope cloud_controller.read,cloud_controller_service_permissions.read,openid,testgroup --authorized_grant_types authorization_code,refresh_token --authorities uaa.resource --redirect_uri https://single-signon.x.y.z/signin-cloudfoundry --autoapprove cloud_controller.read,cloud_controller_service_permissions.read,openid,testgroup --secret myTestApp
         And you run: cf cups myOAuthService -p "{\"client_id\": \"myTestApp\", \"client_secret\": \"myTestApp\", \"uri\": \"uaa://uaa.x.y.z\"}"
         # deploy single-signon app
-        And you run: dotnet restore
         And you run: dotnet publish -f netcoreapp2.1 -r ubuntu.16.04-x64
         And you run in the background: cf push -f manifest.yml -p bin/Debug/netcoreapp2.1/ubuntu.16.04-x64/publish
         And you wait until CloudFoundry app single-signon is started
@@ -155,7 +151,6 @@ Feature: CloudFoundry Single SignOn
         And you run: uaac client add myTestApp --scope cloud_controller.read,cloud_controller_service_permissions.read,openid,testgroup --authorized_grant_types authorization_code,refresh_token --authorities uaa.resource --redirect_uri https://single-signon.x.y.z/signin-cloudfoundry --autoapprove cloud_controller.read,cloud_controller_service_permissions.read,openid,testgroup --secret myTestApp
         And you run: cf cups myOAuthService -p "{\"client_id\": \"myTestApp\", \"client_secret\": \"myTestApp\", \"uri\": \"uaa://uaa.x.y.z\"}"
         # deploy single-signon app
-        And you run: dotnet restore
         And you run: dotnet publish -f net461 -r win10-x64
         And you run in the background: cf push -f manifest-windows.yml -p bin/Debug/net461/win10-x64/publish
         And you wait until CloudFoundry app single-signon is started