Hey there! Let's work through this 503 error issue step by step—since you're using Code First with Migrations, there are a few key things to check for your someee.com deployment:

1. Fix Your Publish Configuration #

First, let's make sure you're using the right publish settings for someee's Windows-based servers:

• Stick with Win x64 (most modern free hosting servers run 64-bit)
• Choose Framework-dependent instead of Self-contained—this keeps your package small and uses the server's pre-installed .NET runtime (free hosts almost always have standard runtimes set up)
• Double-check your target framework matches what someee supports (e.g., if you're using .NET 6/7, confirm the server has that runtime installed; some free hosts might be a bit behind on newer versions)

2. Code First Database Setup (No Local DB File Needed!) #

You don't need to upload your local database file—Code First is designed to create/update the database automatically, but you need to configure this correctly for the host:

• Update your connection string in appsettings.json (or web.config if using .NET Framework) to use someee's provided SQL Server credentials. When you create your site on someee, they'll give you a unique database username, password, and server address—plug those into your connection string.
• Make sure your app runs migrations on startup. In your Program.cs (or Startup.cs for older .NET versions), add this code if it's missing:

  // For .NET 6+
  using var scope = app.Services.CreateScope();
  var dbContext = scope.ServiceProvider.GetRequiredService<YourDbContext>();
  dbContext.Database.Migrate(); // Runs pending migrations when the app starts
  

• If someee blocks automatic migrations (some free hosts restrict this), generate a SQL script locally and run it via their database tool:
  1. Run dotnet ef migrations script -o migration.sql in your local project folder (make sure you have the EF Core CLI installed)
  2. Copy the contents of migration.sql
  3. Paste and execute it in someee's database admin panel (look for a "SQL Editor" or similar section)

3. Dig Into Error Logs for the Real Issue #

A 503 is a generic "service unavailable" error—you need to see the actual problem:

• Log into your someee dashboard, find your site, and look for a "Logs" or "Error Logs" section. This will show you specific exceptions (like invalid connection strings, missing runtime, or permission issues)
• If logs aren't available, temporarily enable detailed error messages in your app:
  Add this to Program.cs:

  app.UseDeveloperExceptionPage();
  

  Important: Turn this off after troubleshooting for security!

4. Ensure Full File Upload #

Partial uploads often cause 503 errors:

• Delete all existing files on the someee server and re-publish your app from scratch
• Double-check that all files (including appsettings.json, wwwroot content, and compiled DLLs) are uploaded completely

Quick Newbie Checklist #

• Updated connection string to use someee's database credentials
• Enabled automatic migrations (or ran the migration script manually)
• Used Framework-dependent, Win x64 publish settings
• Checked host error logs for specific issues

Start with verifying your connection string and checking the logs—those are the most common culprits for Code First deployment issues on free hosts. Good luck!

内容的提问来源于stack exchange，提问作者Voli