Member Avatar for vinayak.v

hi...
i have released one application..

now i have to maintain the document for the released application..

which is the best method to write the information
such as in word,or pdf or excel or
is there any way to keep the document..?

so that every one should know that the new release
application is released .. and they should be updated

i've hosted the previous application and now i have
release the modules in that application ..

now i have inform all the user that we have
released new modules with etc etc features ..

which is the best way to inform the user about newly released application..?

  • 2 Contributors
  • 5 Replies
  • 185 Views
  • 2 Days Discussion Span
  • Latest Post Latest Post by ArtistScope

Dani AI

Generated

A compact, practical checklist that complements the thread so far (notably ’s idea of exposing version information and ’s publish/release folders).

Keep documentation as a single source of truth in version control (Markdown or plain text). Export user-facing docs as HTML and PDF for easy distribution and search indexing; avoid Word/Excel as the only canonical copy. Maintain a short, human-readable changelog (one line per release) and a machine-readable version endpoint the app can poll.

Deployment handoff checklist:

  • Build/tag the release in source control and produce a single release package (publish artifacts only) plus an MD5/SHA checksum.
  • Include one-page release notes and a detailed PDF install/upgrade guide.
  • Add database migration scripts, the exact execution order, and a backup of the prior schema/state (do not include production credentials).
  • Provide production-ready config (web.config transforms), .NET/IIS target versions, app-pool identity, required file/folder permissions, and any scheduled tasks.
  • Give step-by-step deployment instructions, smoke tests (URLs to hit), expected success criteria, and a rollback procedure with the previous package.
  • Schedule a maintenance window with the hosting team and list a single point of contact and an SLA for post-deploy verification.

Notification options and a minimal implementation pattern:

  • Public changelog page + downloadable PDF for users.
  • Email to a subscribers list for major releases.
  • In-app automatic update check that polls a small JSON endpoint; show a concise "What's new" dialog linking to the release notes.

Example minimal version endpoint (host at /version.json):

{
  "version": "1.2.3",
  "build": 456,
  "notesUrl": "/releases/1.2.3-notes.html",
  "downloadUrl": "/releases/app-1.2.3.zip"
}

Cautions: never send production credentials via plain email, always test on staging, verify checksums after transfer, and require the hoster to run the smoke tests and confirm success. This set of artifacts and steps will make hosting handoffs predictable and keep users reliably informed.

Member Avatar for ArtistScope

Version update notices are usually maintained by polling an online record of the current version number.

So now you have 2 methods to notify users:

- pop a window from within the application
- send an update invitation by email

Some installer makers include the option of using their ready made version/update checkers.

Member Avatar for vinayak.v

thanks for replying..

sorry for one more stupid Question

There are two teams hosting team and development team

developers build the software and related document before release

they have the code and document.

now what is the process to that builded project to the hosters i.e hosting department..

means... what are the steps that we should keep in mind

before we give the project to the hosters.....??

Member Avatar for ArtistScope

Are you talking about an ASP application? I hope, so otherwise you are in the wrong forum.

So your team has written an ASP application which is related to web hosting and you have different members in your team responsible for administrating the hosting?

Yet you are worried about how you can notify clients that an update is available for your application?

Member Avatar for vinayak.v

yes u got it right its an asp hosting..
i have two folders publish and release folder..
i want to give to the hoster for hosting..

now what is the process to give the publish release
folder to the hosters..

what steps we need to take..

Member Avatar for ArtistScope

What does the application do?

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.