home.social

#office365 — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #office365, aggregated by home.social.

  1. Acá tiene que haber un error.

    Estoy en #LibreOffice 26.2, trabajando en un documento de #MicrosoftWord (de extensión «.docx»). Son 21 páginas, poco texto, nada de imágenes. Su tamaño es de menos de 70 KB. Hasta acá, todo normal.

    Ahora, se me da por guardarlo como #OpenDocument («.odt») y termina pesando ¡¡¡más de 75 MB!!! :akko_aaa:

    ¡¿Cómo puede ser?! :mindblown:

    #Office365 #TheDocumentFoundation

  2. Acá tiene que haber un error.

    Estoy en #LibreOffice 26.2, trabajando en un documento de #MicrosoftWord (de extensión «.docx»). Son 21 páginas, poco texto, nada de imágenes. Su tamaño es de menos de 70 KB. Hasta acá, todo normal.

    Ahora, se me da por guardarlo como #OpenDocument («.odt») y termina pesando ¡¡¡más de 75 MB!!! :akko_aaa:

    ¡¿Cómo puede ser?! :mindblown:

    #Office365 #TheDocumentFoundation

  3. Acá tiene que haber un error.

    Estoy en 26.2, trabajando en un documento de (de extensión «.docx»). Son 21 páginas, poco texto, nada de imágenes. Su tamaño es de menos de 70 KB. Hasta acá, todo normal.

    Ahora, se me da por guardarlo como («.odt») y termina pesando ¡¡¡más de 75 MB!!! :akko_aaa:

    ¡¿Cómo puede ser?! :mindblown:

  4. Acá tiene que haber un error.

    Estoy en #LibreOffice 26.2, trabajando en un documento de #MicrosoftWord (de extensión «.docx»). Son 21 páginas, poco texto, nada de imágenes. Su tamaño es de menos de 70 KB. Hasta acá, todo normal.

    Ahora, se me da por guardarlo como #OpenDocument («.odt») y termina pesando ¡¡¡más de 75 MB!!! :akko_aaa:

    ¡¿Cómo puede ser?! :mindblown:

    #Office365 #TheDocumentFoundation

  5. Had to edit a #text document in #Office365. It s not often i do that, because luckily most of my work is in more modern formats.
    Out of sheer curiosity, i tried the Editor's suggested "#Refinements" for #Clarity and Vocabulary.

    They were 100% #crap.

    #Microslop

  6. SPFx Deployment Demystified: Step-by-Step for Developers Who Mean Business

    686 words, 4 minutes read time.

    The world of SharePoint Framework (SPFx) development has come a long way since its inception, but for many developers, the process of deploying and managing these solutions remains shrouded in
    mystery.

    Introduction

    As a developer, understanding SPFx deployment is crucial to delivering high-quality, scalable, and secure solutions. In this article, we’ll delve into the step-by-step process of deploying SPFx projects, covering the key considerations, technical nuances, and best practices that will help you master this essential skill.

    Pre-Deployment Planning

    Before embarking on your deployment journey, it’s essential to plan carefully. This involves understanding your target environment, identifying any dependencies or prerequisites, and choosing the right tools and resources for the job.

    const manifest = require('./manifest.json');console.log(manifest);

    Setting Up Your Environment

    To deploy an SPFx solution, you’ll need to set up your development environment. This includes installing the necessary tools, such as Yeoman, gulp, and the SharePoint Framework CLI.

    npm install -g @microsoft/generator-sharepointgulp new project

    Building and Packaging Your Solution

    Once you’ve set up your environment, it’s time to build and package your SPFx solution. This involves creating a package file (.sppkg) that contains all the necessary files and dependencies.

    gulp package-solution

    Deploying Your Solution

    The deployment process itself is where things can get complex. You’ll need to consider factors such as security, permissions, and scalability. In this section, we’ll explore some best practices for deploying SPFx solutions in a production environment.

    const deploy = require('@microsoft/sp-deployment-webpack');deploy(manifest, { env: 'prod' });

    Post-Deployment Tasks

    After deployment, there are several tasks to complete. These include configuring security settings, testing the solution, and monitoring performance.

    const config = require('./config.json');console.log(config);

    Best Practices and Patterns

    Throughout this article, we’ve highlighted some key considerations for deploying SPFx solutions. However, there are many more best practices and patterns to explore. In this section, we’ll discuss some additional strategies for improving the overall quality and
    reliability of your deployments.

    Reflection / Challenge

    • What are some common pitfalls or challenges you’ve encountered when deploying SPFx solutions in the past?
    • How do you ensure that your solution is scalable and secure in a production environment?
    • Can you think of any additional tools or resources that would make the deployment process easier or more efficient?

    Conclusion / Next Steps

    Deploying SPFx solutions requires careful planning, attention to detail, and a deep understanding of the underlying technology. By following the steps outlined in this article, you’ll be well on your way to mastering this critical skill. However, there’s always more to learn, so we recommend exploring additional resources and best practices for continued growth and improvement.

    Next Steps: Take some time to review the code examples and best practices outlined in this article. Experiment with different deployment scenarios and test your skills on a small project before tackling a larger solution. And don’t be afraid to ask questions or seek guidance from more experienced developers!

    Call to Action

    If this post sparked your creativity, don’t just scroll past. Join the community of makers and tinkerers—people turning ideas into reality with 3D printing. Subscribe for more 3D printing guides and projects, drop a
    comment
    sharing what you’re printing, or reach out and tell me about your latest project. Let’s build together.

    Sources

    Disclaimer:

    The views and opinions expressed in this post are solely those of the author. The information provided is based on personal research, experience, and understanding of the subject matter at the time of writing. Readers should consult relevant experts or authorities for specific guidance related to their unique situations.

    Related Posts

    Rate this:

    #MicrosoftGeneratorSharepoint #azure #bestPractices #cloudSolutions #configJson #deployment #deploymentScript #devEnvironment #devops #environmentVariables #Gulp #gulpNewProject #gulpPackageSolution #gulpWebpack #JavaScript #management #manifestJson #microsoft365 #nodejs #npmInstall #npmUpdate #office365 #onPremisesDeployment #patterns #performanceMonitoring #productionEnvironment #reliability #scalability #security #securitySettings #sharepointAdministration #SharePointFramework #sharepointFrameworkCli #SharePointScalability #SharePointSecurity #softwareDevelopment #solutionPackage #SPFxDevelopment #sppkgFile #testing #WebDevelopment #webpackBundle #Yeoman

  7. Ne plus subir les #diktats de #Microsoft. C'est ce qui a poussé la #région #Occitanie, qui regroupe 13 #départements et plus de 6 millions d'#habitants, à chercher une #alternative à la #suite-collaborative du premier #éditeur #mondial. Alors qu'elle s'était équipée d'#Office-365 durant la #crise du #Covid, la région se trouve confrontée trois ans après, lors du renouvellement du #contrat, à des #conditions #commerciales qui la poussent à étudier des #solutions de rechange. « Nous faisions face à une hausse des #coûts de 20 à 30%, alors que nos #budgets de #fonctionnement sont, eux, en train de se contracter. Par ailleurs, nous voulions revenir à un #numérique plus #souverain ; avec Microsoft, nous avions l'impression de ne plus décider de notre #avenir », indique #Nelly-Mallet, la #directrice #adjointe #services #utilisateurs au sein de la #direction de l'#information et du #numérique de la #collectivité. « Par exemple, Microsoft ne nous demandait pas notre #avis sur l'arrivée de l'#IA dans la solution. De son #point-de-vue, la #technologie faisait partie du #package », souligne #Nejla-Yucel, cheffe de #projet #transition-numérique à la région Occitanie.
    https://www.lemondeinformatique.fr/actualites/lire-la-region-occitanie-s-arrache-de-l-influence-des-gafam-94316.html

  8. Forscher des Cloud-Sicherheits-Startups Wiz warnen Unternehmen, die #Microsofts #M365-Plattform nutzen, eindringlich: Der gestohlene Microsoft #Azure AD Enterprise Signing Key verschaffte #chinesischen #Hackern Zugang zu Daten, die über #Exchange Online und #Outlook.com hinausgehen.

    #hacker #china #office365 #vulnerability #azure