search

andrewdavey / postal

Email sending for asp.net mvc using the view engine system to render emails.
http://aboutcode.net/postal
MIT License
536 stars 168 forks source link

Install-Package : Input string was not in a correct format. #171

Open lsardinas opened 7 years ago

lsardinas commented 7 years ago

When I try to install Postal in the Package Manager console I get the error below

Install-Package : Input string was not in a correct format.

Jhonust commented 8 months ago

Double-check the syntax and ensure it matches the required format for installing Postal in the Package reach out to Apk Manager console. If the problem persists.

Jhonust commented 8 months ago

Postal using the Package Manager console. The "Input string was not in a correct format" error typically indicates a formatting issue with the input data. Double-check the command you're using and ensure that plusapk download all parameters are correctly formatted. If the issue persists, you might want to seek assistance from the Postal community or consult the documentation for troubleshooting tips.

pauljhonson614 commented 7 months ago

Awesome work thanks for sharing this Lotus365 info with us.

jacobmark51 commented 6 months ago

It seems like there might be a formatting issue with the input string. Double-checking the Cashmere Scarves format could help resolve this error.

jackgray72 commented 5 months ago

Great info it really helped me a lot thanks for sharing this Beflik info with us.

jenniferhopkin12 commented 2 months ago

This error often occurs when there’s a formatting issue with the package name or version. Double-check your command Latest WhatsApp for typos or ensure that all parameters are correctly specified.

jackgray72 commented 1 week ago

It is like you’re running into a formatting issue with the package command. Double-check the syntax you're using, especially any quotes or version numbers tiro al palo tenis. If you're specifying a version, make sure it’s in the correct format, like "1.0.0" instead of just 1.0.0. If it still doesn’t work, try running the command in an elevated PowerShell window or check for any hidden characters in the string. Hopefully, that clears it up.