-
Notifications
You must be signed in to change notification settings - Fork 811
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Installation issue with "Run as a Stand-Alone Site" option #119
Comments
Hi @WesterfieldM, v4.3.0 was just released which removes the /Tests folder. This was a planned feature, but never implemented. Upgrading to the latest source code should resolve this issue: https://github.com/mspnp/AzureNamingTool/wiki/v4.3.0
|
I believe I’m missing something.
There’s no web.config in the root of wwwroot.
Maybe I’m configuring the web site incorrectly?
***@***.***
***@***.***
***@***.***
Milton Westerfield
317-875-4676 or ext. 16675
From: Bryan Soltis ***@***.***>
Sent: Wednesday, November 20, 2024 9:27 AM
To: mspnp/AzureNamingTool ***@***.***>
Cc: Westerfield, Milton ***@***.***>; Mention ***@***.***>
Subject: [EXT] Re: [mspnp/AzureNamingTool] Installation issue with "Run as a Stand-Alone Site" option (Issue #119)
Hi @WesterfieldM, v4. 3. 0 was just released which removes the /Tests folder. This was a planned feature, but never implemented. Upgrading to the latest source code should resolve this issue: https: //github. com/mspnp/AzureNamingTool/wiki/v4. 3. 0
Hi @WesterfieldM<https://urldefense.com/v3/__https:/github.com/WesterfieldM__;!!KX1o3_mqyiM!o15IIQw9GswQtoYACmG2J6I2RdU_y9KH04MLwp_iuFj2bjAJ-j4pyrdvAFCRSrbnSrx9InCIO23n9NJL8BGaFbm597g$>,
v4.3.0 was just released which removes the /Tests folder. This was a planned feature, but never implemented. Upgrading to the latest source code should resolve this issue:
https://github.com/mspnp/AzureNamingTool/wiki/v4.3.0<https://urldefense.com/v3/__https:/github.com/mspnp/AzureNamingTool/wiki/v4.3.0__;!!KX1o3_mqyiM!o15IIQw9GswQtoYACmG2J6I2RdU_y9KH04MLwp_iuFj2bjAJ-j4pyrdvAFCRSrbnSrx9InCIO23n9NJL8BGa_NJCBJA$>
* Bryan
—
Reply to this email directly, view it on GitHub<https://urldefense.com/v3/__https:/github.com/mspnp/AzureNamingTool/issues/119*issuecomment-2488728070__;Iw!!KX1o3_mqyiM!o15IIQw9GswQtoYACmG2J6I2RdU_y9KH04MLwp_iuFj2bjAJ-j4pyrdvAFCRSrbnSrx9InCIO23n9NJL8BGa5WuYZy4$>, or unsubscribe<https://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/BNB4X5SUKVSAATW2TXDKATD2BSLZ5AVCNFSM6AAAAABSCDYQP2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOBYG4ZDQMBXGA__;!!KX1o3_mqyiM!o15IIQw9GswQtoYACmG2J6I2RdU_y9KH04MLwp_iuFj2bjAJ-j4pyrdvAFCRSrbnSrx9InCIO23n9NJL8BGaH4OKOZI$>.
You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>
|
I'm not sure of the exact issue you may be encountering. Are you attempting to host the site with IIS? This may provide some guidance on ensuring your environment is correct: https://learn.microsoft.com/en-us/aspnet/core/host-and-deploy/iis/?view=aspnetcore-8.0 After configuring your server, you would run the command you referenced. dotnet publish -c Release --property:PublishDir=c:\sites\Ant Just as a suggestion (if possible), running the site in a container may prove much easier, as everything will be installed on the container image. https://github.com/mspnp/AzureNamingTool/wiki/Run-as-a-Docker-Image If you can provide more details on your environment, experience, and errors, I'll try to see if I can help.
|
Tool version
v4.2.1
Describe the bug
while running the following command I'm getting this error
dotnet publish -c Release --property:PublishDir=c:\sites\Ant
C:\Program Files\dotnet\sdk\8.0.404\NuGet.targets(465,5): error MSB3202: The project file "C:\sites\tests\AzureNamingTo
ol.UiTests\AzureNamingTool.UiTests.csproj" was not found. [C:\sites\AzureNamingTool\AzureNamingTool.sln]
C:\Program Files\dotnet\sdk\8.0.404\NuGet.targets(465,5): error MSB3202: The project file "C:\sites\tests\AzureNamingTo
ol.UnitTests\AzureNamingTool.UnitTests.csproj" was not found. [C:\sites\AzureNamingTool\AzureNamingTool.sln]
To Reproduce
Steps to reproduce the behavior:
download the v4.2.1 package
extract it to a folder c:\AzureNamingTool
Open command prompt and navigate to c:\AzureNamingTool
run the following command.
dotnet publish -c Release --property:PublishDir=c:\sites\Ant
Expected behavior
The application to be installed into the c:\sites\Ant directory.
Screenshots
If applicable, add screenshots to help explain your problem.
Installation Method
Stand-Alone Site
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: