Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Example to Input Data

Open
  • Is something wrong?
#418 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
csharp
Domain
documentation

Research direction

Start with the Invoice Sample and the existing documentation, then trace the CreateInvoice() and CustomProperty examples mentioned in the issue. Determine whether MVC/Razor form values can populate the invoice data and generate a Word file, and document the relevant resources or usage path.

Written by the indexing model from the issue text.

Description

I'm wondering if there is a way to set this up using an intranet. I was looking at the Invoice Sample, and it's actually spot on with what I am looking to do. I just can't figure out the best way to hook this up so that I can just input the information into some text fields or other controls (radio button, etc.). I use MVC/Razor web pages to input data for other stuff, and I was thinking to leverage that to just fill in the Invoice data and then click a button to generate a Word file.

I was thinking to just try using a call to, for example, CreateInvoice() on a button click and then hooking my models properties in to replace the CustomProperty, but it isn't that easy, is it? So, something like:

templateDoc.AddCustomProperty( new CustomProperty( "InvoiceNumber", new invoiceNumber ) );

Basically, I am just trying to determine if DocX would work for me before I go further, and needed to test it out.

Does anyone know of any resources to accomplish something like this. I tried looking through the documentation but nothing stood out. If I missed something obvious forgive me in advance.

Dominant language
C#
Stars
1.9k
Forks
483
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from xceedsoftware/DocX

All issues in xceedsoftware/DocX

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.